Liquid Speech BalloonWordPress extension · Lqd
CVE-2019-17070
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 · uneditedThe liquid-speech-balloon (aka LIQUID SPEECH BALLOON) plugin before 1.0.7 for WordPress allows XSS with Internet Explorer.
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 confidenceThe LIQUID SPEECH BALLOON WordPress plugin before version 1.0.7 contains a Cross-Site Scripting (XSS) vulnerability that specifically affects Internet Explorer browsers. The CVSS 6.1 score indicates a network-exploitable, low-complexity attack requiring user interaction, likely reflecting a reflected XSS vector.
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
Liquid Speech BalloonWordPress extension
= 1.0.5CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Confirm plugin installationNavigate to WordPress admin dashboard under Plugins > Installed Plugins, or check the wp-content/plugins/ directory for a folder named 'liquid-speech-balloon' or 'liquid-speech-balloon-premium'.Affected if The plugin folder exists in the WordPress plugins directory.
-
Identify installed versionOpen the main plugin PHP file (typically liquid-speech-balloon.php) or the readme.txt file in the plugin folder and locate the version declaration comment or the 'Version:' field in the plugin header.Affected if The detected version is 1.0.5 or any version prior to 1.0.7.
-
Verify vulnerability contextConfirm that the WordPress site may be accessed by users running Internet Explorer browsers, as this XSS vulnerability specifically targets IE.Affected if Internet Explorer users interact with pages serving the affected plugin components.
-
Inspect affected endpointReview plugin source code for unsanitized parameters in GET or POST requests that reflect user input back into HTML output without proper escaping, commonly found in shortcode handlers or AJAX callbacks.Affected if The plugin contains code that echoes request parameters directly into HTML pages without sanitization.
You are affected if the liquid-speech-balloon plugin is installed at version 1.0.5 (or any version before 1.0.7) and your site serves users running Internet Explorer browsers who can trigger the reflected XSS vector.
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 liquid-speech-balloon plugin to version 1.0.7 or later to remediate the XSS vulnerability. If the plugin is no longer needed, remove it entirely.
Fix this in Liquid Speech Balloon
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17070 — 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-2019-17070 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