CVE-2020-25444
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 · uneditedCross Site Scripting (XSS) vulnerability in Booking Core - Ultimate Booking System Booking Core 1.7.0 via the (1) "About Yourself” section under the “My Profile” page, " (2) “Hotel Policy” field under the “Hotel Details” page, (3) “Pricing code” and “name” fields under the “Manage Tour” page, and (4) all the labels under the “Menu” section.
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 confidenceStored Cross Site Scripting (XSS) vulnerability in Booking Core 1.7.0 allows authenticated users to inject malicious JavaScript via multiple form fields including the 'About Yourself' section in My Profile, 'Hotel Policy' field in Hotel Details, 'Pricing code' and 'name' fields in Manage Tour, and all labels in the Menu section.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.7.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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.
-
Identify Booking Core installationLocate the Booking Core application files on your server or check the web application fingerprint.Affected if Booking Core is not installed, this CVE does not apply.
-
Verify the installed versionCheck your Booking Core installation for the version number. Common locations include the admin dashboard 'About' page, a version file in the application root, or the composer.json file.Affected if The installed version is exactly 1.7.0, the version is affected. If the version is different (higher or lower), the specific flaw may not exist.
-
Confirm user authentication is enabledCheck if the user registration and login functionality is active on your Booking Core site, as this vulnerability requires an authenticated user account.Affected if Authentication is disabled and no user accounts exist, the attack surface for this XSS is significantly reduced.
-
Inspect the My Profile 'About Yourself' fieldLog in as an authenticated user, navigate to the My Profile section, and examine the 'About Yourself' or biography text input field.Affected if The field accepts and stores unsanitized HTML or JavaScript characters, indicating a potential XSS vulnerability.
-
Inspect Hotel Details 'Hotel Policy' fieldAs an authenticated user with hotel management access, navigate to Hotel Details and examine the Hotel Policy text field.Affected if The field accepts and stores unsanitized HTML or JavaScript characters, indicating a potential XSS vulnerability.
Your environment is affected if Booking Core version 1.7.0 is installed, user authentication is enabled, and any of the mentioned form fields accept unsanitized input that could store malicious scripts.
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 context-aware output encoding and implement input validation with strict allowlists for all user-supplied data in the affected fields. The vendor patch should be applied when available.
- 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-2020-25444 — 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-2020-25444 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