CVE-2026-25435
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpdevart Booking calendar, Appointment Booking System booking-calendar allows Stored XSS.This issue affects Booking calendar, Appointment Booking System: from n/a through <= 3.2.36.
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 stored cross-site scripting (XSS) vulnerability exists in the wpdevart Booking Calendar plugin where user-supplied input in booking forms is not properly sanitized before being stored and displayed. When administrators or other users view booking records, the injected malicious JavaScript executes, potentially allowing session hijacking or privilege escalation.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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 wpdevart Booking Calendar plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'wpdevart Booking Calendar' in the list. Note the installed version number displayed next to the plugin name.Affected if The plugin is installed and active
-
Compare installed version to affected releasesDocument the installed version number. Check the WordPress plugin repository or the vendor changelog for the version that includes the XSS fix (typically a version released after the CVE publication date).Affected if Installed version is older than the patched version and booking forms are in use
-
Confirm booking forms are exposedVisit the public-facing pages or posts where the wpdevart Booking Calendar shortcode or widget is embedded. Verify that the booking form accepts user input and can be submitted by visitors.Affected if Booking forms are publicly accessible and accepting submissions
-
Inspect booking records for suspicious inputIn WordPress admin, navigate to the Booking Calendar menu (typically under Booking Calendar > Bookings or similar). Review recent booking records, looking for HTML tags, script tags, or JavaScript event handlers (like onerror, onload, javascript:) in fields such as name, email, phone, or custom fields.Affected if Any booking records contain raw HTML, script tags, or javascript: URIs in input fields
A user is affected if the wpdevart Booking Calendar plugin is installed, the installed version predates the patched release, booking forms are publicly accessible, and malicious script payloads exist in stored booking records.
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 dataApply the latest plugin update which should include proper input sanitization (sanitize_text_field, esc_html, esc_attr) for all booking form fields and output encoding when displaying booking data. If no update is available, disable the plugin until a patched version is released.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25435 — 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-25435 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