dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-48242

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in wpWax Legal Pages legal-pages allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Legal Pages: from n/a through <= 1.4.5.

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 wpWax Legal Pages plugin (versions <=1.4.5) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to sensitive functionality or administrative features within the plugin.

MitigationUpdate to the latest patched version of the Legal Pages plugin; if no patched version is available, restrict administrative access, disable the plugin, or implement server-level access controls 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify installed Legal Pages plugin version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate the 'Legal Pages' (or wpWax Legal Pages) plugin, and note the version number displayed. Alternatively, inspect the plugin's main PHP file (e.g., /wp-content/plugins/legal-pages/lp-main.php or similar) and look for the 'Version:' header comment.
    Affected if The displayed version is 1.4.5 or lower, or if no version is displayed and the plugin has not been updated to a version higher than 1.4.5.
  2. Verify plugin is active
    In the WordPress admin under Plugins > Installed Plugins, confirm that the Legal Pages plugin shows as 'Active'. Only active plugins expose their functionality to potential exploitation.
    Affected if The plugin is active and the version is 1.4.5 or lower.
  3. Check for publicly accessible plugin endpoints
    Inspect the plugin directory structure (typically /wp-content/plugins/legal-pages/) for PHP files that handle administrative or sensitive functions. Test common admin-action endpoints (e.g., ?action=legal_pages_* or admin.php?page=legal-pages*) without authentication using a browser or curl to see if they return sensitive data or allow configuration changes.
    Affected if The plugin exposes administrative functionality or AJAX actions that can be accessed without proper authorization checks, or if unauthenticated requests return administrative data.
  4. Review user role and capability settings
    Navigate to the plugin's settings page (usually under Settings > Legal Pages or a dedicated Legal Pages menu) and examine any access control, permission, or visibility settings configured within the plugin. Check if public access is granted to restricted pages or features.
    Affected if The plugin settings allow unauthenticated or low-privilege users to access features that should be restricted to administrators.
  5. Audit plugin capabilities file
    Locate and inspect the plugin's main class or capabilities definition file (search for files containing 'capability', 'roles', or 'access' within the plugin directory). Determine if proper role or capability checks are performed before executing sensitive operations.
    Affected if The plugin lacks proper capability checks (e.g., 'manage_options' verification) before allowing access to administrative features.

The environment is affected if the wpWax Legal Pages plugin version is 1.4.5 or lower AND the plugin is active with publicly accessible endpoints or insufficient access control enforcement.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of the Legal Pages plugin; if no patched version is available, restrict administrative access, disable the plugin, or implement server-level access controls until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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