dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32487

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-13
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
Missing Authorization vulnerability in raratheme Lawyer Landing Page lawyer-landing-page allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Lawyer Landing Page: from n/a through <= 1.2.7.

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

A Missing Authorization vulnerability exists in the raratheme Lawyer Landing Page WordPress theme (versions <= 1.2.7). The vulnerability stems from incorrectly configured access control security levels, potentially allowing unauthenticated or low-privilege users to access administrative functions or sensitive operations that should require proper authorization.

MitigationUpdate the Lawyer Landing Page theme to the latest patched version. If no patch is available, review and harden access control configurations, or replace the theme with a secure alternative.

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. Identify if Lawyer Landing Page theme is installed
    Navigate to wp-content/themes/ in your WordPress installation directory and check if a folder named 'lawyer-landing-page' or similar exists. Alternatively, in WordPress admin go to Appearance > Themes to list installed themes.
    Affected if The 'Lawyer Landing Page' theme by raratheme is present in the themes directory.
  2. Determine the installed theme version
    Open the style.css file within the theme folder (wp-content/themes/lawyer-landing-page/style.css) and look for the 'Version:' header in the file comments. Alternatively, check theme details in WordPress admin under Appearance > Themes.
    Affected if The version number displayed is 1.2.7 or lower.
  3. Check for exposed admin AJAX actions
    Review the theme's functions.php file for add_action('wp_ajax_...) calls that handle administrative operations. Test by sending a request to /wp-admin/admin-ajax.php with suspected action names using a low-privilege or unauthenticated account.
    Affected if AJAX actions that should require admin privileges (like modifying settings, users, or content) respond successfully to unauthenticated or subscriber-level requests.
  4. Inspect admin page access controls
    Examine theme PHP files for admin_menu or admin_init hooks and verify they include capability checks using current_user_can() or role checks. Look for pages added via add_menu_page or add_submenu_page without proper authorization gates.
    Affected if Admin functions or pages exist without capability checks like 'manage_options' or are accessible to users with low privileges like 'edit_posts'.
  5. Test sensitive endpoint accessibility
    Using a browser or HTTP tool, attempt to access theme-related endpoints that should be restricted (such as theme settings pages, import/export functions, or custom admin routes) while logged out or as a low-privilege user.
    Affected if Endpoints that should require administrator-level access return 200 OK and expose functionality to unauthenticated or low-privilege users.

A user is affected if the Lawyer Landing Page theme version is 1.2.7 or lower AND sensitive admin functions or pages are accessible without proper 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.

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

Update the Lawyer Landing Page theme to the latest patched version. If no patch is available, review and harden access control configurations, or replace the theme with a secure alternative.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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