CVE-2026-32378
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 Book Landing Page book-landing-page allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Book 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 confidenceA missing authorization vulnerability exists in the raratheme Book Landing Page WordPress theme (versions through 1.2.7). The theme has incorrectly configured access control security levels that allow attackers to exploit improperly enforced authorization checks, likely enabling unauthorized access to administrative functions or sensitive operations that should require higher privileges.
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.
-
Verify if the raratheme Book Landing Page theme is installedAccess the WordPress admin dashboard and navigate to Appearance > Themes, or inspect the wp-content/themes directory for a folder named similar to 'raratheme-book-landing-page' or containing 'rara' theme filesAffected if The theme is present in the WordPress installation
-
Determine the installed theme versionCheck the theme's style.css file in the theme folder for the 'Version:' header, or view the theme details in WordPress admin under Appearance > ThemesAffected if A version number is displayed in the theme metadata
-
Compare the installed version against the affected rangeCompare the discovered version number to the affected range (versions through 1.2.7). Any version 1.2.7 or earlier is within the affected rangeAffected if The version is 1.2.7 or any earlier version number (e.g., 1.2.6, 1.2.0, 1.0.0)
-
Confirm the theme is actively enabledCheck the WordPress admin under Appearance > Themes to see which theme is currently activated and marked as activeAffected if The Book Landing Page theme is activated as the current theme
The environment is affected if the raratheme Book Landing Page theme is installed, enabled, and the version is 1.2.7 or earlier.
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 dataUpdate to version 1.2.8 or later if available; otherwise contact the vendor for an official patch. As a temporary mitigation, restrict access to the affected theme functionality via server-level access controls or disable the theme until a fix is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32378 — 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-32378 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