AmeliaWordPress extension · Tms Outsource
CVE-2023-50860
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 TMS Booking for Appointments and Events Calendar – Amelia allows Stored XSS.This issue affects Booking for Appointments and Events Calendar – Amelia: from n/a through 1.0.85.
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 XSS vulnerability in the Amelia WordPress plugin (Booking for Appointments and Events Calendar) allows attackers to inject malicious JavaScript through unsanitized input fields. The payload persists in the database and executes when administrators or users view booking-related pages, potentially leading to session hijacking or privilege escalation.
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
AmeliaWordPress extension
<= 1.0.85CVSS 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.
-
Verify Amelia plugin versionIn WordPress admin, go to Plugins > Installed Plugins > find Amelia (or 'Tms Outsource Amelia') and check the version number displayed under the plugin nameAffected if The installed version is 1.0.85 or lower
-
Check for active booking functionalityNavigate to Amelia > Appointments or Amelia > Customers in the WordPress admin panel to see if booking data existsAffected if The plugin is actively used with customer bookings and appointments stored
-
Inspect booking input fields for unsanitized dataView existing customer/booking records in the Amelia dashboard. Check fields such as customer name, email, phone, and custom fields for any unexpected characters or script tags (<script>, javascript:, onerror=, etc.)Affected if Any booking records contain raw HTML or script tags in input fields that render unescaped in the admin interface
-
Review page source for unescaped outputOpen a booking-related admin page (e.g., Amelia > Appointments), view the page source (right-click > View Page Source), and search for customer-supplied data that appears without HTML entity encodingAffected if Customer names or other input fields display raw characters like < > " instead of their encoded equivalents (< > ")
You are affected if the Amelia plugin version is 1.0.85 or lower AND booking data with potentially malicious input is present in the system, as the XSS payload would execute when viewing booking-related pages in the admin panel.
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 dataUpdate the Amelia plugin to version 1.0.86 or later. Additionally, implement proper input validation and output encoding for all user-supplied data before rendering in HTML contexts.
Fix this in Amelia
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50860 — 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-2023-50860 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