dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-7401

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WordPress Premium Age Verification plugin (versions up to 3.0.2) contains an arbitrary file read/write vulnerability in remote_tunnel.php due to insufficiently protected remote support functionality. Unauthenticated attackers can read sensitive files or write malicious content, potentially leading to RCE.

MitigationUpdate to the patched version of the plugin immediately. If no patch is available, disable or remove the remote_tunnel.php file and review server logs for signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Premium Age Verification plugin directory
    Check the WordPress plugins folder (wp-content/plugins/) for a directory named 'premium-age-verification' or similar variant containing 'age-verification' in the name
    Affected if The plugin directory exists in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (usually premium-age-verification.php or similar) and look for the Version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry
    Affected if The version is 3.0.2 or lower (any version up to and including 3.0.2 is affected)
  3. Verify the vulnerable file exists
    Check for the presence of remote_tunnel.php within the plugin directory (typically wp-content/plugins/premium-age-verification/remote_tunnel.php or similar path)
    Affected if The file remote_tunnel.php exists in the plugin folder
  4. Confirm the remote support functionality is exposed
    Attempt to access the remote_tunnel.php file via HTTP/HTTPS request (e.g., visit yourdomain.com/wp-content/plugins/[plugin-folder]/remote_tunnel.php) and verify it returns a response rather than a 404 error
    Affected if The remote_tunnel.php file is directly accessible over the web (does not return 404 or require authentication)
  5. Review access logs for exploitation attempts
    Search web server access logs (Apache, Nginx, or WAF logs) for any requests to remote_tunnel.php, especially those containing file parameter patterns (e.g., ?file= or ?path=)
    Affected if There are logged requests to remote_tunnel.php with suspicious file parameter patterns

The environment is affected if the Premium Age Verification plugin version is 3.0.2 or lower AND the remote_tunnel.php file exists and is web-accessible, enabling unauthenticated arbitrary file read/write operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the patched version of the plugin immediately. If no patch is available, disable or remove the remote_tunnel.php file and review server logs for signs of exploitation.

Recommended fix High confidence

Version 3.0.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Premium Age Verification / Restriction for WordPress'
  4. Check if the current version is 3.0.2 or below
  5. If vulnerable, click 'Update Now' to update to the latest version (3.0.3 or higher)
  6. Verify the update completed successfully
  7. Confirm the running version is 3.0.3 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7401 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data