dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-29004

HIGH · 8.8 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Privilege Assignment vulnerability in AA-Team Premium Age Verification / Restriction for WordPress, AA-Team Responsive Coming Soon Landing Page / Holding Page for WordPress allows Privilege Escalation.This issue affects Premium Age Verification / Restriction for WordPress: from n/a through 3.0.2; Responsive Coming Soon Landing Page / Holding Page for WordPress: from n/a through 3.0.

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 · moderate confidence

Two WordPress plugins by AA-Team (Premium Age Verification/Restriction and Responsive Coming Soon Landing Page) contain an Incorrect Privilege Assignment vulnerability allowing privilege escalation. The plugins fail to properly enforce role-based access controls, permitting lower-privileged users or potentially unauthenticated attackers to gain administrative access.

MitigationUpdate both plugins to their latest versions (beyond 3.0.2 for Premium Age Verification and beyond 3.0 for Responsive Coming Soon). Until patches are available, restrict administrative access to trusted users only and monitor user role changes.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check if Premium Age Verification plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect /wp-content/plugins/ directory for folders containing 'aa-team' or 'age-verification' or 'premium-age-verification'
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify Premium Age Verification version
    Check the plugin's main PHP file (usually in the plugin folder) for a Version header in the plugin comment block, or view the plugin details in WordPress Plugins > Installed Plugins
    Affected if Version is 3.0.2 or lower (any version up to and including 3.0.2)
  3. Check if Responsive Coming Soon plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect /wp-content/plugins/ directory for folders containing 'coming-soon' or 'responsive-coming-soon'
    Affected if The plugin folder exists in the WordPress plugins directory
  4. Identify Responsive Coming Soon version
    Check the plugin's main PHP file for a Version header, or view the plugin details in WordPress Plugins > Installed Plugins
    Affected if Version is 3.0 or lower (any version up to and including 3.0)
  5. Verify if vulnerable plugins are active
    In WordPress admin > Plugins > Installed Plugins, check if either affected plugin has an 'Activate' or 'Active' status
    Affected if Either plugin shows as Active (the vulnerability requires the plugin to be enabled to be exploitable)

You are affected if either the Premium Age Verification plugin (version 3.0.2 or lower) or the Responsive Coming Soon plugin (version 3.0 or lower) is installed and active on your WordPress site.

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 both plugins to their latest versions (beyond 3.0.2 for Premium Age Verification and beyond 3.0 for Responsive Coming Soon). Until patches are available, restrict administrative access to trusted users only and monitor user role changes.

Recommended fix Moderate confidence

Premium Age Verification: 3.0.3+; Responsive Coming Soon: 3.1+

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'AA-Team Premium Age Verification / Restriction' and check if update to version 3.0.3 or later is available
  4. If update available, click 'Update Now' to install the patched version
  5. Repeat for 'AA-Team Responsive Coming Soon Landing Page' and update to version 3.1 or later if available
  6. Alternatively, download the latest versions from the WordPress plugin repository or AA-Team's official source
  7. After updating, verify the plugins are functioning correctly on the frontend and backend
  8. Review user roles and capabilities to ensure no unauthorized privilege escalation occurred

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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