CVE-2025-15364VulnerabilityPublished 6 Jan 2026Updated 8 Apr 2026

CVE-2025-15364: Download Manager (WordPress plugin) · Missing Support for Integrity Check

Affects Download Manager (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.3High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% 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:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
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: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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 6 Jan 2026
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 26 Oct 2026.

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
codename065Download Manager	Affected <=3.3.40	Fixed in–

AI-suggested

Until an official fix is released, users should consider restricting access to the plugin or disabling it if possible. Monitoring for suspicious account changes and applying principle of least privilege to user roles may help reduce risk. Avoid using affected versions of the plugin in production environments if feasible.

Description

The Download Manager plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.3.40. This is due to the plugin not properly validating a user's identity prior to updating their details like password. This makes it possible for unauthenticated attackers to change user's passwords, except administrators, and leverage that to gain access to their account.

Impact

An attacker can perform privilege escalation by changing passwords of non-administrator users without authentication, leading to unauthorized account takeover. This compromises user confidentiality, integrity, and availability of affected accounts. Administrator accounts are not vulnerable to this attack vector. There are no reports of active exploitation in the wild.

Summary

CVE-2025-15364 is a privilege escalation vulnerability in the codename065 Download Manager WordPress plugin. The flaw arises from inadequate validation of user identity when updating account details, specifically passwords. This allows unauthenticated attackers to change passwords of users other than administrators, effectively taking over those accounts. The vulnerability is identified as CWE-353 (missing support for integrity checks). It affects all versions up to 3.3.40. The CVSS 3.1 base score is 7.3, with attack vector network, low attack complexity, no privileges required, no user interaction, and impacts on confidentiality, integrity, and availability.

CWE-353Missing Support for Integrity Check (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
Architecture and Design
Add an appropriately sized checksum to the protocol, ensuring that data received may be simply validated before it is parsed and used.
Implementation
Ensure that the checksums present in the protocol design are properly implemented and added to each message before it is sent.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
OWASP ASVS 4.0.3
V10.3.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Content Spoofing Via Application API Manipulation (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Apr 2026, 21:21 UTC

WeaknessesCWE-353

Technical details

References

Community reviews

Related threats