Web3Press <= 3.2.0 - Authenticated (Contributor+) Arbitrary File Read
Strategic Overview
- Status
- Patched in 3.3.0
- Affected Plugin
- Web3Press – Migrating to 3ook.com Decentralized Bookstore
- Affected Version
<= 3.2.0- CVSS
- 6.5Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-46527
At a glance
CVE-2025-46527 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Web3Press WordPress plugin, affecting versions <= 3.2.0. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.3.0; sites on affected versions should update now. Disclosed May 2025, reported by ch4r0n.
Vulnerability Overview
The Web3Press – Decentralize Publishing with Writing NFT plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 3.2.0. This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in Web3Press <= 3.2.0 takes an account at Contributor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Web3Press the fix is 3.3.0: builds <= 3.2.0 are affected, anything from 3.3.0 onward is not.
Remediation
Update to version 3.3.0, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Web3Press 3.3.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C