dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-47241

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-02
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
Missing Authorization vulnerability in CoCart Headless CoCart – Headless ecommerce cart-rest-api-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CoCart – Headless ecommerce: from n/a through <= 3.11.2.

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

Missing authorization vulnerability in CoCart WordPress plugin (versions up to 3.11.2) allows unauthenticated attackers to access certain API endpoints due to incorrectly configured access control security levels. The plugin fails to properly validate user authorization before allowing access to cart-related functionality.

MitigationImplement proper authorization checks on all API endpoints and ensure access control security levels are correctly configured according to the principle of least privilege. Update to the latest version if available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Confirm CoCart plugin is installed
    Navigate to WordPress admin > Plugins and locate 'CoCart' in the list of installed plugins, or check the /wp-content/plugins/cocart directory exists on the server
    Affected if CoCart plugin is installed and active on the WordPress site
  2. Identify installed CoCart version
    Check the plugin version listed in the WordPress plugins admin page, or inspect the main plugin file (e.g., cocart.php) to find the 'Version' header comment
    Affected if Installed version is 3.11.2 or lower, or any version prior to the patched release
  3. Test API endpoint accessibility without authentication
    Send a GET request to the CoCart REST API endpoint (typically /wp-json/cocart/v2/cart or /wp-json/cocart/v2/products) using a tool like curl or Postman without providing any authentication credentials (no nonce or session token)
    Affected if The API returns valid cart or product data without requiring authentication, indicating the endpoint is publicly accessible
  4. Verify WordPress REST API authentication configuration
    Check WordPress settings under Settings > CoCart (if available) or inspect the plugin code for 'permission_callback' functions in REST API route definitions to confirm authorization checks are present
    Affected if The plugin's REST API routes lack proper permission_callback functions or allow 'authenticated' => false for sensitive endpoints

A site is affected if CoCart version 3.11.2 or lower is installed AND sensitive cart-related API endpoints respond to unauthenticated requests without proper authorization validation.

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

Implement proper authorization checks on all API endpoints and ensure access control security levels are correctly configured according to the principle of least privilege. Update to the latest version if available.

Recommended fix Moderate confidence

3.11.3 or latest available version

  1. 1. Log in to your WordPress admin dashboard.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate CoCart – Headless ecommerce (cart-rest-api-for-woocommerce).
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. After updating, verify the plugin is working correctly by testing your headless e-commerce cart functionality.
  6. 6. Confirm the new version is >= 3.11.3
Caveat Review CoCart changelog for any deprecated features or required configuration changes after upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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