Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | The CVSS 3.1 score of 5.3 reflects a moderate-severity issue with important contextual factors: the attack vector is network-based (AV:N), attack complexity is low (AC:L), no privileges are required (PR:N), and no user interaction is needed (UI:N), indicating an easily exploitable vulnerability from an attack perspective. However, the impact scope is unchanged (S:U) with no confidentiality loss (C:N), limited integrity impact (I:L), and no availability impact (A:N), meaning attackers cannot exfiltrate data or cause outages. The integrity-only impact (ability to modify but not read or delete) suggests the real-world risk depends heavily on the criticality of the data being protected. Without EPSS score or KEV status data provided, the exploitation likelihood cannot be precisely quantified; however, authorization flaws in plugins are frequently targeted once disclosed. The lack of complexity and privilege requirements makes this a genuine priority, but the limited integrity scope prevents it from being critical. Organizations running this plugin should treat this as a medium-to-high priority remediation target. |
| Exploit ScenarioDerived | An attacker discovers the vulnerable Book Landing Page plugin active on a WordPress site and crafts a simple HTTP request (GET or POST) to the unprotected endpoint without authentication credentials. The attacker modifies the landing page content, injecting malicious text, phishing links, or promotional content that is immediately published to site visitors. Because the attack requires no interaction from legitimate users and the endpoint is network-accessible with low complexity, the attacker can automate bulk modifications across multiple affected sites, affecting search engine rankings, user trust, and potentially serving as a vector for subsequent social engineering or credential harvesting attacks. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 13, 2026
Improper access control in raratheme Book Landing Page through version 1.2.7 permits unauthenticated attackers to modify content or data without proper authorization checks. The vulnerability stems from missing authentication validation on protected operations, allowing remote exploitation without user interaction. No patch is currently available.
Earlier versions of this analysis (1)
A missing authorization vulnerability exists in raratheme's Book Landing Page plugin (versions up to 1.2.7) that allows unauthenticated attackers to modify sensitive data through incorrectly configured access control mechanisms. The vulnerability has a CVSS score of 5.3 with network-based attack vector and no privilege requirements, enabling integrity compromise without authentication. While the CVSS score is moderate and there is no indication of active exploitation in the wild, the lack of access controls represents a fundamental security misconfiguration that could allow unauthorized content manipulation.
RemediationAI
The primary remediation is to upgrade the Book Landing Page plugin to version 1.2.8 or later, which should include proper authorization checks on all data-modifying endpoints. Users should immediately apply the patch through their WordPress dashboard (Plugins > Installed Plugins > Book Landing Page > Update) or via WordPress CLI (wp plugin update book-landing-page). As an interim workaround until patching is possible, administrators should disable the plugin and reactivate it only after upgrading, or restrict access to wp-admin and plugin endpoints using web application firewall (WAF) rules or .htaccess restrictions to limit exposure. Additionally, conduct a security audit of recent changes to book landing pages to identify any unauthorized modifications that may have occurred, and consider implementing role-based access controls at the application level to enforce least-privilege principles.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability stems from CWE-862 (Missing Authorization), a class of flaws where software fails to properly verify that a user has permission to perform a requested action before executing it. The Book Landing Page plugin, developed by raratheme, implements endpoint handlers or functionality that accept user requests without sufficient authorization checks. The affected component likely manages book landing page content, metadata, or configuration through web-accessible endpoints that do not validate user privileges or session tokens. This is typical in WordPress plugin architectures where custom post types or admin AJAX actions are exposed without proper capability checks (wp_verify_nonce, current_user_can, etc.). The vulnerability affects versions 1.2.7 and earlier, suggesting the authorization framework may have been added or improved in later versions.
Know when Book Landing Page gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
Missing 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.
Executive ViewAI
CVE-2026-32378 presents moderate security risk, a missing authorization vulnerability rated CVSS 5.3. Attackers could gain access beyond their authorized level. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-11880
NVD
CVE.org
EPSS
VulDB
GitHub PoC
Exploit-DB