Skip to main content

Booking Package EUVDEUVD-2026-100763

| CVE-2026-103425 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-14 Wordfence GHSA-rm22-89fc-8hj5
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain contributor-level account
  2. Delivery
    Submit crafted 'id' parameter payload
  3. Exploit
    Payload stored without sanitization
  4. Execution
    Admin/user views injected page
  5. Persist
    Script executes in victim browser
  6. Impact
    Session hijack or privilege actions

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated WordPress account with contributor-level privileges or higher (PR:L), making open or weakly-controlled contributor registration a key enabling factor; without such an account the flaw cannot be reached. The attacker injects a payload via the plugin's 'id' parameter, and the stored script only executes when another user subsequently loads the injected page - so impact depends on a higher-privileged user (e.g., an administrator) viewing that content. The limiting factors are therefore: mandatory authentication at contributor level, reliance on a victim visiting the affected page, and the Booking Package plugin (versions ≤1.7.29) being installed and active.

Impact

This is a moderate-severity stored XSS (CVSS 6.4) whose real-world priority is tempered by its authentication requirement. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) confirms network-based, low-complexity exploitation but requires PR:L - the description specifies contributor-level access and above, so this is an authenticated vulnerability, not an unauthenticated internet-facing bug. The scope change (S:C) and C:L/I:L reflect that injected script executes in other users' browser context, potentially including higher-privileged users (e.g., an admin viewing the injected page), which is the primary escalation concern. No EPSS score was provided in the input, there is no CISA KEV listing, and no public exploit code is referenced, so there is no evidence of active or widespread exploitation at this time. Overall this is a legitimate but not emergency-grade issue: it depends on an attacker already holding a contributor account, which limits its utility to insider/compromised-account scenarios or sites with open contributor registration. Patch/mitigation prioritization should sit below unauthenticated RCE or admin-takeover flaws but above purely theoretical issues.

Exploit ScenarioDerived

An attacker who holds (or registers for) a contributor-level WordPress account submits content to the Booking Package plugin with a malicious payload in the 'id' parameter, which is stored without sufficient sanitization or output escaping. When an administrator or other user later views the affected page, the script executes in their browser, enabling session/cookie theft or actions performed as that higher-privileged user. No public proof-of-concept exploit is referenced in the provided data.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Stored cross-site scripting in the Booking Package WordPress plugin (versions up to and including 1.7.29) allows authenticated users with contributor-level access or higher to inject persistent JavaScript via the 'id' parameter, which executes when other users view the injected page. The flaw results from insufficient input sanitization and output escaping, and no public exploit has been identified at time of analysis. Exploitation requires an authenticated contributor account, and the impact is constrained to higher-privileged users who access the malicious content, making this a moderate-severity issue.

RemediationAI

Upstream fix available (changeset 3728015); released patched version not independently confirmed. Users should update the Booking Package plugin to the latest version available from the WordPress plugin repository. The fix is referenced in the Trac changeset at https://plugins.trac.wordpress.org/changeset/3728015/booking-package/trunk/index.php. If immediate patching is not possible, consider disabling the plugin until an update can be applied. As a mitigating control, restrict contributor-level accounts to trusted users and monitor for suspicious content, noting that these measures may impact site functionality and require additional administrative oversight. The Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/10293e5a-15ea-42c1-a0df-b95f723a75a3?source=cve provides further guidance.

Affected VersionsENISA

Booking Package 0 ≤1.7.29

Affected Packages

euvd booking_package no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This is a stored cross-site scripting (XSS) vulnerability classified as CWE-79, affecting the Booking Package plugin for WordPress. The plugin fails to properly sanitize the 'id' parameter and escape output, allowing an authenticated attacker with contributor-level privileges (PR:L in the CVSS vector) to store malicious scripts in the site's database. When a higher-privileged user, such as an administrator, later views the compromised page, the script executes in their browser. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N indicates network exploitability, low attack complexity, and a scope change (S:C), meaning the vulnerability in the plugin can affect resources beyond its own security context, potentially leading to broader site compromise. The specific vulnerable code locations are highlighted in the plugin's index.php at lines 1789, 1802, 1099, and 260, as referenced in the Wordfence advisory and Trac links. The CPE cpe:2.3:a:masaakitanaka:booking_package:*:*:*:*:*:*:*:* confirms that all versions are potentially affected.

Know when Booking Package 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

Vendor (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Network-reachable, low-complexity stored XSS requiring a contributor account (PR:L); scope changes (S:C) as script runs in other users' browser context with limited C/I impact and no availability effect.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

DescriptionCVE.org

The Booking Package plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'id' parameter in all versions up to, and including, 1.7.29 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Low
niche WordPress booking plugin, limited install base
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy