WordPress WP EasyPay plugin <= 4.5.4 - Path Traversal vulnerability
WP EasyPay plugin by Saad Iqbal, version 4.5.4 and earlier, is affected. The fix is in version 4.5.5, so update to 4.5.5 or later.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 4.5.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Unauthenticated Path Traversal in WP EasyPay <= 4.5.4 versions.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- wp-easy-pay
through 4.5.4
References 1
Questions about CVE-2026-39734
What does this mean?
A path traversal flaw lets attackers escape the website's folder and access private files stored elsewhere on the server.Source: patchstack.com
Am I affected, and how do I check?
Versions 4.5.4 and earlier of the WP EasyPay plugin by Saad Iqbal are affected, and no specific setup conditions are listed. To check, compare the plugin version shown on the WordPress Plugins screen with 4.5.4.Source: patchstack.com
What should I do about it?
Update WP EasyPay to version 4.5.5 or later.Source: patchstack.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data