dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-49403

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Arbitrary File Download in Premium Age Verification / Restriction for WordPress <= 3.0.2 versions.

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 Premium Age Verification/Restriction WordPress plugin versions 3.0.2 and below contains an unauthenticated arbitrary file download vulnerability. Attackers can exploit this flaw without any authentication to download sensitive files from the server, potentially exposing configuration files, credentials, or other confidential data.

MitigationUpdate the Premium Age Verification/Restriction plugin to a version beyond 3.0.2 if a patched release is available; otherwise, disable or remove the plugin until a fix is released.

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
None
Availability
None

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

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. Verify Premium Age Verification/Restriction plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Premium Age Verification/Restriction' or 'Premium Age Verification' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to 'premium-age-verification' or 'age-restriction'.
    Affected if The plugin is installed and present in the WordPress environment
  2. Check the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the plugin name to view its details, or check the plugin's main PHP file header for the 'Version' comment. Compare the version number to '3.0.2' - any version 3.0.2 or lower is affected.
    Affected if The plugin version is 3.0.2 or lower
  3. Confirm the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify whether the Premium Age Verification/Restriction plugin shows as 'Active'. Only active plugins can be exploited.
    Affected if The plugin is active and running on the site

If the Premium Age Verification/Restriction plugin is installed, active, and running version 3.0.2 or lower, the environment is vulnerable to unauthenticated arbitrary file downloads.

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 the Premium Age Verification/Restriction plugin to a version beyond 3.0.2 if a patched release is available; otherwise, disable or remove the plugin until a fix is released.

Recommended fix Moderate confidence

Latest version available (beyond 3.0.2)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Premium Age Verification / Restriction for WordPress'
  4. Check if an update is available and update to the latest version
  5. If no update is shown in WordPress, manually download the latest version from the official WordPress plugin repository or the vendor's website and reinstall

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49403 — 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-49403 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