Skip to main content
CVE-2025-4578VulnerabilityPublished

CVE-2025-4578: File Provider (WordPress plugin) · SQL Injection

Affects File Provider (WordPress plugin)Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Unknown File ProviderAffected
  • =0
Fixed in–

AI-suggested

Immediate mitigation steps should include disabling or removing the File Provider plugin until a secure patched version is released. Organizations should monitor official plugin repositories and security advisories for updates addressing CVE-2025-4578. In the interim, web application firewalls (WAFs) can be configured with custom rules to detect and block suspicious AJAX requests targeting the vulnerable parameter. Security teams should conduct thorough audits of their WordPress installations to identify the presence of the File Provider plugin and assess exposure. Implementing strict input validation and sanitization at the application level is critical once patches are available. Additionally, organizations should ensure that database user permissions are minimized to reduce the potential impact of SQL injection attacks. Regular backups and incident response plans should be reviewed and updated to prepare for potential exploitation scenarios. Finally, continuous monitoring for unusual database queries or web traffic patterns can help detect exploitation attempts early.

Description

The File Provider WordPress plugin through 1.2.3 does not properly sanitise and escape a parameter before using it in a SQL statement via an AJAX action available to unauthenticated users, leading to a SQL injection

References

Community reviews

Loading reviews…