CVE-2025-34085VulnerabilityPublished 9 Jul 2025Updated 16 Jul 2025

CVE-2025-34085: Element Engage Simple File List WordPress Plugin

Affects Element Engage Simple File List WordPress PluginSource CVE Database V5

Not known to be exploited.

Data as of 3 Aug 2025, 00:37 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: High
Subsequent system integrity: High
Subsequent system availability: High

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.
Subsequent system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Subsequent System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Subsequent System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jul 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

AI-suggested

Organizations should immediately audit their WordPress installations to identify the presence of the Simple File List plugin. Until an official patch is released, it is advisable to disable or uninstall the plugin to eliminate exposure. Implement network-level protections such as web application firewalls (WAFs) with rules to detect and block suspicious requests targeting file management endpoints. Restrict access to WordPress admin and plugin directories via IP whitelisting or VPN access where feasible. Monitor web server and application logs for unusual activity indicative of exploitation attempts. Employ file integrity monitoring to detect unauthorized changes to files managed by the plugin. Additionally, ensure regular backups are performed and stored securely offline to enable recovery in case of data loss or ransomware attacks. Stay informed through vendor advisories for patch releases and apply updates promptly once available. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation patterns related to this vulnerability.

Impact

For European organizations, this vulnerability poses a significant threat due to the widespread use of WordPress and its plugins across various sectors including government, education, healthcare, and commerce. Exploitation could lead to unauthorized access to sensitive documents, disruption of online services, and compromise of data integrity and confidentiality. This is particularly critical for organizations subject to GDPR and other stringent data protection regulations, as breaches could result in severe legal and financial penalties. The potential for availability impact also threatens business continuity and service reliability. Given the plugin's role in file management, attackers could leverage this vulnerability to distribute malware or ransomware within organizational networks, amplifying the risk. The remote, no-authentication nature of the vulnerability means attackers can exploit it at scale, increasing the likelihood of widespread incidents affecting multiple European entities.

Summary

CVE-2025-34085 is a vulnerability identified in the Simple File List WordPress Plugin developed by Element Engage LLC. Although specific technical details and affected versions are not provided, the CVSS 4.0 vector string indicates a highly severe vulnerability. The vector AV:N (Attack Vector: Network) implies the vulnerability can be exploited remotely over the network without physical access. AC:L (Attack Complexity: Low) and AT:N (Attack Authentication: None) indicate that exploitation requires no special conditions or authentication, making it easy for attackers to leverage. UI:N (User Interaction: None) means no user interaction is needed, further increasing the risk. The vulnerability impacts confidentiality (VC:H), integrity (VI:H), and availability (VA:H) at a high level, with scope (S) and impact on security requirements (SI and SA) also rated high, suggesting a broad and critical impact on the system's security posture. The absence of known exploits in the wild and patch links suggests this is a newly published vulnerability with no public exploit yet, but the potential for severe damage is significant given the CVSS vector. The Simple File List plugin is commonly used to manage and share files within WordPress sites, so a vulnerability here could allow attackers to access, modify, or delete sensitive files, potentially leading to data breaches, defacement, or denial of service. The lack of detailed technical information limits precise attack scenario descriptions, but the CVSS vector strongly suggests a remote code execution or critical file manipulation vulnerability that does not require authentication or user interaction.

Community reviews

Loading reviews…