CVE-2024-35667
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 · uneditedMissing Authorization vulnerability in WP EasyCart.This issue affects WP EasyCart: from n/a through 5.5.19.
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 confidenceThis is a Missing Authorization vulnerability in WP EasyCart WordPress plugin affecting versions through 5.5.19. The vulnerability allows attackers to bypass access controls and perform actions they are not authorized to perform, likely due to missing capability checks or nonce verification on sensitive functionality within the plugin.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify WP EasyCart plugin is installedCheck your WordPress installation under wp-content/plugins/ for the wp-easycart directory, or log into the WordPress admin and navigate to Plugins > Installed Plugins to confirm WP EasyCart appears in the list.Affected if WP EasyCart plugin is not found in the plugins directory or plugin list.
-
Determine installed WP EasyCart versionOpen the main plugin file (wp-content/plugins/wp-easycart/wpeasycart.php) and locate the version header in the file comments, or check the version listed in the WordPress admin plugin page.Affected if The version shown is 5.5.19 or any earlier version (versions through 5.5.19 are affected).
-
Confirm plugin is activeIn the WordPress admin, go to Plugins > Installed Plugins and verify that WP EasyCart shows as 'Active' rather than 'Inactive'.Affected if The plugin is active and the version is 5.5.19 or earlier.
-
Check for sensitive AJAX handlersInspect the plugin directory for AJAX action handlers (typically in files named like ajax.php, or functions using add_action('wp_ajax_...')). Look for sensitive operations that lack current_user_can() capability checks or nonce verification.Affected if Sensitive AJAX handlers exist without proper authorization checks (this confirms the vulnerability condition).
If WP EasyCart is installed, active, and running version 5.5.19 or earlier, the environment is affected by this missing authorization vulnerability.
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 WP EasyCart to the latest version which should contain proper authorization checks. If no update is available, audit the plugin code for all AJAX handlers and admin actions to add current_user_can() capability checks and nonce verification.
- 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-35667 — 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-35667 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