Premium Age Verification / Restriction for WordPress <= 3.0.2 - Unauthenticated Arbitrary File Read and Write via remote_tunnel.php
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Premium Age Verification / Restriction for WordPress
- Affected Version
<= 3.0.2- CVSS
- 9.8Critical
- Weakness type
- CWE-798 · Use of Hard-coded Credentials
- CVE
CVE-2025-7401
At a glance
CVE-2025-7401 is a critical-severity Use of Hard-coded Credentials vulnerability in the Premium Age Verification / Restriction for WordPress WordPress plugin, affecting versions <= 3.0.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2025, reported by ch4r0n.
Vulnerability Overview
The Premium Age Verification / Restriction for WordPress plugin for WordPress is vulnerable to arbitrary file read and write due to the existence of an insufficiently protected remote support functionality in remote_tunnel.php in all versions up to, and including, 3.0.2. This makes it possible for unauthenticated attackers to read from or write to arbitrary files on the affected site's server which may make the exposure of sensitive information or remote code execution possible.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-798: Use of Hard-coded Credentials
The product contains hard-coded credentials, such as a password or cryptographic key.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Premium Age Verification / Restriction for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C