CVE-2024-37935
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 anhvnit Woocommerce OpenPos allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Woocommerce OpenPos: from n/a through 6.4.4.
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 confidenceMissing authorization vulnerability in Woocommerce OpenPos plugin allows unauthenticated or low-privilege attackers to access functionality that should be restricted by Access Control Lists (ACLs). This ACL bypass enables unauthorized access to privileged operations 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the OpenPos plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'openpos' or 'woocommerce-openpos'. Inspect the main plugin file (usually openpos.php or index.php) to confirm the plugin name and version.Affected if The plugin folder exists and the version declared in the plugin header is below 6.4.4 (or if no version is displayed, the plugin is present).
-
Read the plugin version from metadataOpen the main OpenPos plugin PHP file and locate the version string in the plugin header comment (typically shown as 'Version: x.x.x' at the top of the file).Affected if The version number retrieved is lower than 6.4.4, indicating the installation is in the vulnerable range.
-
Inspect WordPress REST API endpointsAccess the WordPress REST API routes by visiting /wp-json/ and look for routes under the 'openpos' namespace. Attempt to call these endpoints without authentication (no valid nonce or session).Affected if The plugin REST API endpoints respond successfully without requiring authentication or capability checks, confirming the ACL bypass is present.
-
Test AJAX action accessibilityUse a tool like curl or Burp to send POST requests to /wp-admin/admin-ajax.php with openpos-related actions (check for 'action' parameters containing 'openpos' or 'pos_') without providing valid authentication tokens.Affected if The AJAX actions execute and return successful responses without requiring login or user capability verification.
The environment is affected if WooCommerce OpenPos is installed with a version lower than 6.4.4 and the plugin's API endpoints are accessible without authentication.
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 Woocommerce OpenPos to the latest version (beyond 6.4.4) which should contain proper authorization checks. If update unavailable, audit the plugin code for endpoints/actions lacking capability checks or nonce validation and add proper access controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37935 — 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-37935 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