dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-8565

HIGH · 8.1 CVSS v3.1 Published 2025-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
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
The Privacy Policy Generator, Terms & Conditions Generator WordPress Plugin : WP Legal Pages plugin for WordPress is vulnerable to unauthorized access of functionality due to a missing capability check on the wplp_gdpr_install_plugin_ajax_handler() function in all versions up to, and including, 3.4.3. This makes it possible for authenticated attackers, with Contributor-level access and above, to install arbitrary repository plugins.

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 missing capability check on the wplp_gdpr_install_plugin_ajax_handler() function. This AJAX endpoint, intended to install plugins from the WordPress repository, can be invoked by any authenticated user with Contributor-level access or higher, bypassing the Administrator-only permission normally required for plugin installation.

MitigationUpdate WP Legal Pages to version 3.4.4 or later which includes the missing capability check. Alternatively, restrict AJAX functionality using server-side capability verification until the update can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Confirm WP Legal Pages plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Legal Pages' or 'Legal Pages' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'wp-legal-pages' or similar.
    Affected if The plugin is not found in the installed plugins list
  2. Identify the installed version
    In WordPress admin Plugins page, click on the plugin name to view details, or check the plugin's main PHP file header for the 'Version' comment. Compare against 3.4.4.
    Affected if Version is lower than 3.4.4
  3. Verify AJAX endpoint is accessible
    Check if the wplp_gdpr_install_plugin_ajax_handler function exists in the plugin files, typically in the main plugin PHP file or an ajax-handler.php file. This function handles the /wp-admin/admin-ajax.php?action=wplp_gdpr_install_plugin request.
    Affected if The AJAX handler function exists in the plugin code
  4. Confirm Contributor-level or higher users exist
    In WordPress admin, go to Users > All Users and review the role column. Check for users with roles of Contributor, Author, Editor, or Administrator.
    Affected if Any user account has Contributor-level access or higher and the plugin version is below 3.4.4

The environment is affected if WP Legal Pages plugin is installed with a version lower than 3.4.4 and has at least one user with Contributor-level access or higher who could invoke the vulnerable AJAX endpoint.

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 WP Legal Pages to version 3.4.4 or later which includes the missing capability check. Alternatively, restrict AJAX functionality using server-side capability verification until the update can be applied.

Recommended fix Moderate confidence

WP Legal Pages version 3.4.4 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate WP Legal Pages (Privacy Policy Generator, Terms & Conditions Generator)
  4. 4. If an update is available, click 'Update Now'
  5. 5. Alternatively, manually download the latest version from wordpress.org/plugins/wplegalpages/ and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the version number reflects the fix (version newer than 3.4.3)

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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