Litespeed CacheWordPress extension · Litespeedtech
CVE-2024-47374
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 LiteSpeed Technologies LiteSpeed Cache litespeed-cache allows Stored XSS.This issue affects LiteSpeed Cache: from n/a through <= 6.5.0.2.
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 LiteSpeed Cache plugin allows authenticated attackers to inject malicious JavaScript code through unsanitized input. The payload is permanently stored in the database and executes when other users access affected pages within the WordPress admin panel or frontend.
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
Litespeed CacheWordPress extension
< 6.5.1CVSS 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.
-
Check LiteSpeed Cache plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find LiteSpeed Cache, or check the version in the plugin's main PHP file header. Alternatively, look for the version in the plugin's readme.txt or in the WordPress plugins database table.Affected if The installed version is any version before 6.5.1 (e.g., 6.5.0.2, 6.4.x, 6.3.x, etc.)
-
Verify LiteSpeed Cache plugin is activeCheck if the LiteSpeed Cache plugin is currently activated in the WordPress site. This can be done via wp-admin > Plugins or by querying the wp_options table for the active_plugins option.Affected if The plugin is active and the version is vulnerable (< 6.5.1)
-
Check for authenticated user accessReview WordPress user roles and capabilities. The vulnerability requires an authenticated attacker with at least subscriber-level access to inject the XSS payload.Affected if The site has user accounts (especially subscriber or higher roles) and the plugin version is vulnerable
-
Search database for suspicious stored entriesQuery the wp_postmeta, wp_options, or other relevant tables in the WordPress database for patterns that may indicate XSS payloads (e.g., script tags, javascript:, onload, onerror attributes). Use: SELECT * FROM wp_postmeta WHERE meta_value LIKE '%<script%' OR meta_value LIKE '%javascript:%'Affected if Any stored entries containing unsanitized script tags or event handlers are found in the database
You are affected if LiteSpeed Cache version is below 6.5.1 and the plugin is active on your WordPress site, regardless of whether you can immediately identify injected payloads.
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.
dbcve · scoped6.5.1
Upgrade LiteSpeed Cache to a version newer than 6.5.0.2. Until patched, implement output encoding and Content Security Policy (CSP) headers to mitigate script execution.
LiteSpeed Cache version 6.5.1
- 1. Create a full backup of your WordPress site (database and files) before performing any updates.
- 2. Navigate to your WordPress admin dashboard > Plugins > Installed Plugins.
- 3. Locate 'LiteSpeed Cache' in the plugin list and click 'Update now' if an update is available, or manually update to version 6.5.1 or later.
- 4. Alternatively, update via WP-CLI: `wp plugin update litespeed-cache` (requires WP-CLI installation).
- 5. Alternatively, download version 6.5.1+ from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin.
- 6. After updating, verify the version number in Plugins > Installed Plugins to confirm version 6.5.1 or higher is installed.
- 7. Clear any caching (LiteSpeed Cache > Toolbox > Cache > Purge All) to ensure the patched code is served.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Litespeed Cache
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47374 — 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-2024-47374 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