CVE-2025-5034VulnerabilityPublished 21 Jun 2025Updated 23 Jun 2025

CVE-2025-5034: wp-file-download · Cross-Site Scripting (XSS)

Affects wp-file-downloadSource CVE Database V5

Not known to be exploited · CVSS 7.1 High · fixed in 6.2.6 : patch wp-file-download soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.2.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
wp-file-download	Affected =0	Fixed in–

AI-suggested

1. Immediate upgrade: Organizations should verify the version of the wp-file-download plugin in use and upgrade to version 6.2.6 or later, where the vulnerability is patched. 2. Input validation and output encoding: Developers and site administrators should ensure that any custom code interacting with the plugin properly sanitizes and escapes user inputs before rendering them in the browser. 3. Web Application Firewall (WAF): Deploy or update WAF rules to detect and block malicious payloads targeting the vulnerable parameter, providing an additional layer of defense while patches are applied. 4. User awareness training: Educate users and administrators about the risks of clicking on suspicious links, especially those that appear to come from untrusted sources. 5. Content Security Policy (CSP): Implement strict CSP headers to limit the execution of unauthorized scripts, mitigating the impact of XSS attacks. 6. Regular vulnerability scanning: Incorporate automated scanning tools that specifically check for XSS vulnerabilities in WordPress plugins to detect similar issues proactively. 7. Monitor logs and alerts: Continuously monitor web server and application logs for unusual activities or repeated attempts to exploit the vulnerability.

Description

The wp-file-download WordPress plugin before 6.2.6 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting

Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on WordPress sites with the wp-file-download plugin installed. Exploitation can lead to session hijacking, allowing attackers to impersonate legitimate users, potentially gaining unauthorized access to sensitive information or administrative functions. This can compromise confidentiality and integrity of data. Additionally, attackers can use the vulnerability to conduct phishing campaigns by redirecting users to malicious sites or injecting fraudulent content, undermining user trust and brand reputation. For organizations handling personal data under GDPR, such breaches could lead to regulatory penalties and legal consequences. The availability impact is generally limited in reflected XSS cases but could be indirectly affected if attackers use the vulnerability to inject disruptive scripts. Given that no authentication is required and user interaction is only needed to click a malicious link, the attack surface is broad. European organizations with customer-facing WordPress sites, especially in sectors like e-commerce, finance, healthcare, and government, are at higher risk due to the sensitive nature of their data and the potential for reputational damage.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/ebd9aa9f-3da9-4457-922f-975bef6e33f8/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jun 2025, 12:53 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats