dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11816

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 Privacy Policy Generator, Terms & Conditions Generator WordPress Plugin : WP Legal Pages plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the disconnect_account_request() function in all versions up to, and including, 3.5.1. This makes it possible for unauthenticated attackers to disconnect the site from its API plan.

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 WP Legal Pages WordPress plugin has a broken access control vulnerability in the disconnect_account_request() function, which lacks a capability check. This allows unauthenticated attackers to trigger this function and disconnect the site from its API plan, causing denial of service to the API connectivity.

MitigationApply the vendor patch (upgrade to version 3.5.2 or later) which adds a proper capability check to the disconnect_account_request() function. Until then, consider disabling the plugin or restricting access at the server level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 WP Legal Pages plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Legal Pages' or check the filesystem at wp-content/plugins/ for the legal-pages folder
    Affected if The plugin is not installed or has been removed
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the version number listed under the WP Legal Pages plugin name, or inspect the main plugin file header at wp-content/plugins/legal-pages/wp-legal-pages.php for the 'Version' tag
    Affected if Version is present and less than 3.5.2 (or version field is missing entirely indicating a very old installation)
  3. Inspect the disconnect_account_request function for capability check
    Examine the plugin source code file containing the disconnect_account_request() function (typically in includes/class-wp-legal-pages.php or similar) and look for a current_user_can() or similar capability check before the function logic executes
    Affected if No capability check (like current_user_can()) is found before the disconnect_account_request function code
  4. Check if REST API endpoint is exposed
    Probe the WordPress REST API endpoint for disconnecting the account (typically /wp-json/wplegal/v1/disconnect or similar) using a tool like curl without authentication: curl -X POST https://yourdomain.com/wp-json/wplegal/v1/disconnect
    Affected if The endpoint responds without requiring authentication (returns 200 instead of 401/403)

A user is affected if the WP Legal Pages plugin is installed with a version earlier than 3.5.2 and the disconnect_account_request function lacks a capability check, allowing unauthenticated API disconnection.

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

Apply the vendor patch (upgrade to version 3.5.2 or later) which adds a proper capability check to the disconnect_account_request() function. Until then, consider disabling the plugin or restricting access at the server level.

Recommended fix High confidence

3.5.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'WP Legal Pages' (Privacy Policy Generator, Terms & Conditions Generator)
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin is running version 3.5.2 or higher

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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