dbcve.org
Litespeed CacheWordPress extension · Litespeedtech

CVE-2022-46800

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 5.3 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cross-Site Request Forgery (CSRF) vulnerability in LiteSpeed Technologies LiteSpeed Cache plugin <= 5.3 versions.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in LiteSpeed Cache plugin versions 5.3 and below allows attackers to trick authenticated administrators into unknowingly executing unintended actions such as clearing cache, modifying plugin settings, or other state-changing operations via maliciously crafted web requests.

MitigationUpdate LiteSpeed Cache plugin to the latest version and implement anti-CSRF token validation on all state-changing endpoints, including proper Origin/Referer header verification.

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
Affected:<= 5.3

CVSS 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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if LiteSpeed Cache plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'LiteSpeed Cache' in the list of active plugins.
    Affected if LiteSpeed Cache plugin is not installed on the WordPress site.
  2. Determine installed LiteSpeed Cache version
    In WordPress admin, go to Plugins > Installed Plugins and click on 'LiteSpeed Cache' to view the plugin details, or check the plugin file header in wp-content/plugins/litespeed-cache/litespeed-cache.php for the 'Version' comment.
    Affected if The installed version is 5.3 or lower.
  3. Verify WordPress admin access exists
    Check if any user accounts with Administrator role exist on the WordPress site by querying the wp_users and wp_usermeta tables, or verify through the WordPress admin user list.
    Affected if The site has administrator-level user accounts that could be targeted by CSRF attacks.
  4. Inspect plugin endpoints for anti-CSRF protection
    Examine the LiteSpeed Cache plugin PHP files for nonce validation or CSRF token checks on state-changing actions. Look for functions like wp_verify_nonce, check_ajax_referer, or custom token validation in files handling cache clearing or settings modifications.
    Affected if No anti-CSRF token validation is found on administrative action endpoints.

A user is affected if LiteSpeed Cache plugin version 5.3 or below is installed and the site has administrator accounts without proper CSRF protections on state-changing plugin actions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.3
Interim mitigation

Update LiteSpeed Cache plugin to the latest version and implement anti-CSRF token validation on all state-changing endpoints, including proper Origin/Referer header verification.

Recommended fix Moderate confidence

LiteSpeed Cache version 5.4 or later

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find LiteSpeed Cache in the plugin list
  4. Check if the current version is 5.3 or below
  5. If vulnerable, click 'Update Now' to update to the latest version, or manually download version 5.4 or later from the WordPress plugin repository
  6. After updating, verify the new version number in the Plugins list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Litespeed Cache Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-46800 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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