dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67974

HIGH · 7.5 CVSS v3.1 Published 2026-02-20
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
Missing Authorization vulnerability in WP Legal Pages WPLegalPages wplegalpages allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPLegalPages: from n/a through <= 3.5.4.

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

Missing Authorization vulnerability in the WordPress WPLegalPages plugin allows unauthenticated or unauthorized users to exploit incorrectly configured access control security levels, potentially enabling them to access administrative functionality or make changes without proper permissions.

MitigationUpdate WPLegalPages plugin to the latest version once available; if no patch exists, implement WordPress capability checks on all plugin admin actions and consider restricting access via server-level authentication 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. Confirm WPLegalPages plugin is installed
    Log in to WordPress admin panel and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the wplegalpages folder
    Affected if WPLegalPages plugin folder exists in the WordPress plugins directory
  2. Identify installed version
    In WordPress admin, find WPLegalPages in the plugins list and note the version number displayed, or open the main plugin PHP file and look for the Version header comment
    Affected if Installed version is lower than the latest available version (once patched version is released)
  3. Verify admin access controls are properly enforced
    Attempt to access WPLegalPages admin pages directly via URL without logging in or with a low-privilege user account, or inspect plugin PHP files for current_user_can() or capability checks before admin actions
    Affected if Admin pages or actions are accessible without proper authentication or without capability verification checks
  4. Check for unauthorized access to plugin settings
    Review the plugin admin menu items and try accessing them with a subscriber-level or non-administrator account, or check the plugin code for missing permission checks on AJAX handlers or form processing
    Affected if Non-administrator accounts can view, modify, or execute WPLegalPages administrative functions without restriction

User is affected if WPLegalPages plugin is installed and allows unauthenticated or low-privilege users to access administrative functionality due to missing authorization checks.

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 WPLegalPages plugin to the latest version once available; if no patch exists, implement WordPress capability checks on all plugin admin actions and consider restricting access via server-level authentication until a fix is released.

Recommended fix Moderate confidence

Latest version of WPLegalPages (version > 3.5.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate WPLegalPages in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is functioning correctly on the site
  6. 6. Test that the authorization controls are working as expected

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-67974 — 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-67974 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