Vigilbase CVEConnect your agent

CVE-2025-34085

Not in CISA KEVCVE-2025-34085

Not confirmed exploited. 2 of 8 rule sources name it; Cloudflare blocks by default.

Edge rules
2/8
Our test
No exploit yet
CVSS
—
EPSS
—
Posts, 14d
02026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts
Published
2025-07-09

Ask Vigil

AI · answers from this page
Ask about CVE-2025-34085: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Public exploits

None found
0 Metasploit0 Exploit-DB0 Scanner template0 GitHub PoCs

No exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.

Timeline

  1. 2025-07-09
    CVE published
    CVE List
  2. 2025-08-11
    Cloudflare ships a rule
    WordPress:Plugin:Simple File List - Remote Code Execution - CVE:CVE-2025-34085
  3. 2025-12-03
    F5 ships a rule
    WordPress Simple File List Plugin Insecure File Upload

Social

2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts

No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.

Vendor statements

Quoted
CloudflareWAF Managed Rules2 quotesBlocks by default

First rule 2025-08-11, 33 days after the CVE was published.

2025-08-11New rule…0341fcccDefault: BlockSource
WordPress:Plugin:Simple File List - Remote Code Execution - CVE:CVE-2025-34085. Previous action: Log. New action: Block. This is a New Detection
2025-08-11New rule…4cefeedaDefault: DisabledSource
WordPress:Plugin:Simple File List - Remote Code Execution - CVE:CVE-2025-34085 - 2. Previous action: Log. New action: Disabled. This is a New Detection
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)1 quoteRule published

First rule 2025-12-03, 147 days after the CVE was published.

2025-12-03New rule200020231Source
Added: signature 200020231 "WordPress Simple File List Plugin Insecure File Upload" (Malicious File Upload, risk High), systems: WordPress. References: CVE-2025-34085, CVE-2020-36847.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.