LiveActive security incident?Get immediate response
CVE Record

CVE-2018-6891: Bookly #1 WordPress Booking Plugin Lite before 14.5 has XSS via a jQuery.ajax request to ng-payment_details...

Bookly #1 WordPress Booking Plugin Lite before 14.5 has XSS via a jQuery.ajax request to ng-payment_details_dialog.js.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-6891 is a cross-site scripting issue in Bookly #1 WordPress Booking Plugin Lite before 14.5. A vulnerable booking site could let attacker-supplied content execute in a user’s browser when affected payment-details functionality is viewed. Business risk depends on whether the plugin is installed and who views the poisoned content.

Executive priority

Prioritize remediation for public booking sites using old Bookly Lite versions, especially where staff or administrators review booking payment details. This is not KEV-backed in the provided data, but stored XSS in WordPress plugins can create account and data exposure risk.

Technical view

The CVE describes XSS tied to a jQuery.ajax request in ng-payment_details_dialog.js. The public report characterizes it as blind stored XSS. The bundle does not provide CVSS, CWE, or complete affected CPE data, so validation should focus on installed Bookly Lite version and plugin behavior rather than broad product assumptions.

Likely exposure

Externally reachable WordPress sites running Bookly Lite before 14.5 are the likely exposure. Sites without the plugin, or running 14.5 or later, are not indicated as affected by the provided sources.

Exploitation context

The sources do not show CISA KEV listing or confirmed active exploitation. The issue is still relevant for legacy WordPress installations because stored XSS can affect administrators or booking staff who view attacker-controlled booking or payment detail data.

Researcher notes

The provided data is sparse: no CVSS vector, CWE, affected CPEs, or vendor advisory text is included. Treat the version boundary and blind stored XSS characterization as source-grounded, but verify against the WordPress plugin changelog and the original researcher post before closing exposure.

Mitigation direction

  • Inventory WordPress sites for the Bookly Lite plugin and installed version.
  • Upgrade Bookly Lite to 14.5 or later where the vendor changelog supports it.
  • Check vendor guidance for any additional cleanup or hardening recommendations.
  • Review stored booking and payment-detail records for suspicious script-like content.
  • Limit administrative access to trusted networks and accounts where feasible.

Validation and detection

  • Confirm whether Bookly Lite is installed on each WordPress site.
  • Record the exact plugin version and compare it with the before-14.5 affected range.
  • Review relevant booking/payment-detail workflows for untrusted stored input exposure.
  • Check web server and WordPress logs for suspicious booking submissions around staff views.
  • Verify no unsupported or abandoned plugin copy remains active.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-6891 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.