VulnerabilityPublished 12 Dec 2025

CVE-2025-12841: Bookit (WordPress plugin) · Missing Authorization

Affects Bookit (WordPress plugin)Source CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: evidence found.
nuclei template: WordPress Bookit < 2.5.1 - Unauthenticated Stripe Settings Update
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Bookit	Affected =0	Fixed in–

AI-suggested

Immediately monitor and audit all changes to Stripe payment configurations within the Bookit plugin to detect unauthorized modifications.
Restrict access to the vulnerable REST endpoint by implementing web application firewall (WAF) rules that block unauthenticated requests targeting the plugin’s API paths.
Apply principle of least privilege by limiting administrative access to WordPress backend and payment settings only to trusted personnel.
Once available, promptly update the Bookit plugin to version 2.5.1 or later where the authorization check is implemented.
Consider temporarily disabling the Bookit plugin or the Stripe payment integration if patching is delayed and risk is unacceptable.
Employ network segmentation and monitoring to detect anomalous API calls or traffic patterns indicative of exploitation attempts.
Educate site administrators about this vulnerability and encourage vigilance regarding unexpected payment configuration changes.
Review and tighten Stripe account security, including API keys and webhook configurations, to minimize impact if plugin settings are altered.

Description

The Bookit WordPress plugin before 2.5.1 has a publicly accessible REST endpoint that allows unauthenticated update of the plugins Stripe payment options.

Impact

For European organizations, this vulnerability poses a risk primarily to the integrity of their payment processing workflows. Unauthorized modification of Stripe payment options could lead to financial losses through redirected payments or fraudulent transactions. While confidentiality and availability are not directly impacted, the trustworthiness of payment data and transaction processing is compromised. This can result in reputational damage, regulatory scrutiny under GDPR due to potential financial fraud, and operational disruption if payment processing is altered or disabled. Organizations in sectors such as hospitality, event management, and e-commerce that use Bookit for booking and payment handling are particularly at risk. The medium severity score reflects a moderate but tangible threat that should not be ignored, especially given the critical nature of payment systems. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks once exploit code becomes available.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/60cb3d5f-1aa5-4858-ab84-07fe7c023fdd/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 11:22 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats