CVE-2026-32381
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 · uneditedMissing Authorization vulnerability in raratheme App Landing Page app-landing-page allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects App Landing Page: from n/a through <= 1.2.2.
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 confidenceThis is a Missing Authorization vulnerability in the raratheme App Landing Page WordPress theme (versions <= 1.2.2) where the application fails to properly enforce access control checks, potentially allowing unauthenticated or lower-privileged users to access functionality or resources they should not have permission to access.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm theme installationNavigate to Appearance > Themes in the WordPress admin dashboard and verify if the 'raratheme App Landing Page' theme is currently installed and active.Affected if The raratheme App Landing Page theme is installed and active on the WordPress site.
-
Check installed theme versionIn the WordPress admin, go to Appearance > Themes, click on the raratheme App Landing Page theme details, and locate the version number displayed in the theme information panel.Affected if The installed version is 1.2.2 or any earlier version.
-
Identify publicly accessible endpointsReview the theme directory for PHP files that contain AJAX handlers (wp_ajax_), admin_init hooks, or REST API endpoints. Use a web vulnerability scanner or manually inspect theme PHP files for functions that process requests without checking user capabilities.Affected if The theme exposes sensitive endpoints or functions that can be accessed without authentication or proper capability verification.
-
Test for unauthorized accessAttempt to access suspected sensitive theme functions or endpoints while logged out (as an unauthenticated user) or with a low-privilege user account (subscriber level). Observe if the requests are processed without returning authorization errors.Affected if Unauthenticated or lower-privileged users can successfully access functionality that should require higher-level permissions.
You are affected if the raratheme App Landing Page theme version 1.2.2 or earlier is installed and exposes sensitive functions or endpoints that can be accessed without proper authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization verification (capability/role checks) on all sensitive functions and endpoints, ensuring that user permissions are validated before executing protected operations.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32381 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32381 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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