dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-1229

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 SimpleShop plugin for WordPress is vulnerable to unauthorized disconnection from SimpleShop due to a missing capability check on the maybe_disconnect_simpleshop function in all versions up to, and including, 2.10.2. This makes it possible for unauthenticated attackers to disconnect the SimpleShop.

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 SimpleShop WordPress plugin has a missing capability check in the maybe_disconnect_simpleshop function, allowing unauthenticated attackers to arbitrarily disconnect the SimpleShop integration. This is a broken access control vulnerability where the function lacks the required current_user_can() check before performing the disconnect action.

MitigationUpdate to SimpleShop version 2.10.3 or later which includes proper capability validation. Until then, consider disabling the plugin or implementing web application firewall rules to block unauthenticated disconnect 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
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 checks

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

  1. Verify SimpleShop plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'SimpleShop' or 'Simple WP' in the list. Note whether it is active or inactive.
    Affected if The SimpleShop plugin is installed and active on the WordPress site.
  2. Check installed SimpleShop version
    In the WordPress plugin list, find the SimpleShop plugin entry and locate the version number displayed below the plugin name. Compare this to version 2.10.3.
    Affected if The installed version is lower than 2.10.3 (e.g., 2.10.2, 2.10.1, 2.10.0, etc.).
  3. Inspect the maybe_dispathc_simpleshop function for capability check
    Access the WordPress site via FTP or file manager, navigate to wp-content/plugins/simpleshop/includes/ or similar directory, and locate the PHP file containing the maybe_disconnect_simpleshop function. Open the file and search for 'function maybe_disconnect_simpleshop' or 'maybe_disconnect'. Examine the function to see if it includes a current_user_can() check before performing the disconnect action.
    Affected if The function exists and performs the disconnect without first verifying user capabilities (no current_user_can() call found at the start of the function).
  4. Test unauthenticated disconnect capability
    Using a tool like curl or Burp Suite, send a POST or GET request to the endpoint that triggers the maybe_disconnect_simpleshop function (commonly an AJAX endpoint like wp-admin/admin-ajax.php?action=simpleshop_disconnect or similar). Send the request without providing any authentication cookies or credentials.
    Affected if The request succeeds and returns a successful response indicating the SimpleShop integration was disconnected, without requiring authentication.

The site is affected if SimpleShop plugin is active with a version lower than 2.10.3 and the maybe_disconnect_simpleshop function lacks a current_user_can() capability check, allowing unauthenticated disconnect 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to SimpleShop version 2.10.3 or later which includes proper capability validation. Until then, consider disabling the plugin or implementing web application firewall rules to block unauthenticated disconnect requests.

Recommended fix Moderate confidence

SimpleShop version 2.10.3 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find SimpleShop plugin in the list
  4. Check if an update is available for SimpleShop
  5. If update available, click 'Update Now' to update to version 2.10.3 or later
  6. Alternatively, manually download SimpleShop version 2.10.3 or later from the WordPress plugin repository and upload via Plugins > Add New > Upload 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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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