dbcve.org
SpeedycacheWordPress extension · Softaculous

CVE-2024-43299

MEDIUM · 5.4 CVSS v3.1 Published 2024-08-26
Fix available
A fix is available. Upgrade to 1.1.9 or later.
See remediation →
61/100
Remediation priority · Elevated
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 Softaculous SpeedyCache speedycache.This issue affects SpeedyCache: from n/a through <= 1.1.8.

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 · high confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in the SpeedyCache WordPress plugin (version 1.1.8 and below). The flaw allows attackers to trick authenticated administrators into performing unintended actions, such as modifying plugin settings or executing administrative functions, by exploiting the lack of anti-CSRF token validation on sensitive operations.

MitigationImplement WordPress nonces (security tokens) on all state-changing forms and AJAX endpoints within the plugin, and verify these nonces on the server side before processing any requests. Additionally, consider adding SameSite cookie attributes and validating Origin/Referer headers as defense-in-depth.

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
SpeedycacheWordPress extension
Affected:< 1.1.9

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
None
Integrity
Low
Availability
Low

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

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. Confirm SpeedyCache plugin is installed and active
    Log into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for SpeedyCache in the list. Also check the /wp-content/plugins/ directory for the speedycache folder.
    Affected if The SpeedyCache plugin is present and activated on the WordPress site
  2. Identify the installed SpeedyCache version
    In WordPress admin, go to Plugins > Installed Plugins and find the SpeedyCache plugin entry to view its version number. Alternatively, open the main plugin file (such as speedycache.php) and locate the Version header in the plugin comment block.
    Affected if The version is 1.1.8 or below (versions prior to 1.1.9)
  3. Locate sensitive plugin actions without nonce validation
    Inspect the plugin source code files, particularly AJAX handlers (usually in ajax.php or similar) and form processing code. Search for state-changing functions and verify whether they call wp_verify_nonce(), check_admin_referer(), or wp_nonce_field() before executing actions.
    Affected if AJAX endpoints or form handlers process requests without validating a security token
  4. Examine plugin forms for missing nonce fields
    In the WordPress admin, navigate to each SpeedyCache settings page. Use browser developer tools to view the HTML source of all forms (especially settings forms, cache clear buttons, and configuration options). Check for hidden input fields containing nonce values such as _wpnonce or _wp_http_referer.
    Affected if Forms that modify plugin settings or execute actions lack hidden nonce input fields

A user is affected if SpeedyCache version 1.1.8 or below is installed and active, and the plugin contains forms or AJAX endpoints that process state-changing requests without validating anti-CSRF tokens.

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 1.1.9 or later
Fixed in 1.1.9
Interim mitigation

Implement WordPress nonces (security tokens) on all state-changing forms and AJAX endpoints within the plugin, and verify these nonces on the server side before processing any requests. Additionally, consider adding SameSite cookie attributes and validating Origin/Referer headers as defense-in-depth.

Recommended fix High confidence

1.1.9

  1. Backup your WordPress site and database before making any changes
  2. Update the SpeedyCache plugin to version 1.1.9 or later via the WordPress admin dashboard under Plugins > Installed Plugins, or download from the WordPress plugin repository
  3. Verify the update was successful by checking the plugin version number
  4. Clear any caching layers if SpeedyCache is active to ensure the patched code is fully deployed

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

Fix this in Speedycache Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43299 — 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-2024-43299 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