CVE-2025-9034: Wp Edit Password Protected · Open Redirect
Affects Wp Edit Password ProtectedSource CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Sep 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Wp Edit Password Protected | Affected
| Fixed in– |
AI-suggested
European organizations should immediately verify if they use the 'Wp Edit Password Protected' plugin and identify the version in use. In the interim, organizations can implement web application firewall (WAF) rules to detect and block suspicious redirect parameters or URLs containing redirect payloads. Additionally, security teams should educate users about the risks of clicking on unexpected or suspicious links, especially those that appear to redirect to unknown domains. Monitoring web server logs for unusual redirect patterns can help detect exploitation attempts. Organizations should also review their email filtering and phishing detection capabilities to reduce the risk of malicious links reaching end users. Finally, developers maintaining WordPress sites should audit custom code and third-party plugins for similar open redirect issues and apply strict URL validation and allowlisting wherever redirects are necessary.
Description
The Wp Edit Password Protected WordPress plugin before 1.3.5 does not validate a parameter before redirecting the user to its value, leading to an Open Redirect issue