dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-3722

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Swift Performance Lite plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on the ajax_handler() function in all versions up to, and including, 2.3.6.18. This makes it possible for authenticated attackers, with subscriber-level access and above, to retrieve and modify settings.

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

The Swift Performance Lite WordPress plugin has a broken access control vulnerability in its ajax_handler() function. The function lacks proper capability checks, allowing any authenticated user with subscriber-level permissions (the lowest WordPress role) to access administrative AJAX endpoints and retrieve or modify plugin settings.

MitigationUpdate to version 2.3.6.19 or later which includes proper capability validation. Alternatively, add current_user_capability checks to the ajax_handler() function before processing any settings-related requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checks

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

  1. Verify Swift Performance Lite plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'swift-performance-lite' or 'swift-performance'. Alternatively, view the installed plugins list in WordPress admin under Plugins > Installed Plugins.
    Affected if The plugin folder exists in wp-content/plugins/
  2. Determine installed plugin version
    Open the main plugin file (usually swift-performance-lite.php or similar in the plugin folder) and locate the version in the plugin header comment, or check the version listed in WordPress admin plugins page.
    Affected if Version is lower than 2.3.6.19 (or version cannot be determined and the plugin is present)
  3. Confirm subscriber-level users exist
    In WordPress admin, go to Users > All Users and check if any users with the 'Subscriber' role exist. Alternatively, query the wp_usermeta table for users with wp_capabilities containing 'a:1:{s:10:"subscriber"'
    Affected if At least one subscriber-level user account exists in the WordPress installation
  4. Verify AJAX endpoint accessibility
    Test the ajax_handler endpoint by sending an authenticated request with a subscriber-level user credential to /wp-admin/admin-ajax.php?action=swift_performance_ajax (or similar plugin AJAX action). Use a tool like curl or Burp Suite to inspect the response.
    Affected if The request returns plugin settings data or executes without returning a capability/error response (response code 200 without permission denial)
  5. Inspect ajax_handler function for capability checks
    If code access is available, review the plugin source code in the ajax_handler() function. Search for 'current_user_can', 'capability', or 'manage_options' checks before processing settings-related AJAX actions.
    Affected if No capability checks are found before processing settings in the ajax_handler function

If the Swift Performance Lite plugin is installed with a version below 2.3.6.19 AND subscriber-level users exist in WordPress, the environment is vulnerable to CVE-2024-3722.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 2.3.6.19 or later which includes proper capability validation. Alternatively, add current_user_capability checks to the ajax_handler() function before processing any settings-related requests.

Recommended fix High confidence

Swift Performance Lite version 2.3.6.19 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate Swift Performance Lite
  4. If an update is available, click 'Update Now'
  5. Alternatively, download version 2.3.6.19 or later from the WordPress plugin repository
  6. Upload the new version via Plugins > Add New > Upload Plugin
  7. Activate the updated plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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