dbcve.org
Woocommerce Order ProposalWordPress extension · Wpovernight

CVE-2024-9927

HIGH · 7.2 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to 2.0.6 or later.
See remediation →
78/100
Remediation priority · High
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 WooCommerce Order Proposal plugin for WordPress is vulnerable to privilege escalation via order proposal in all versions up to and including 2.0.5. This is due to the improper implementation of allow_payment_without_login function. This makes it possible for authenticated attackers, with Shop Manager-level access and above, to log in to WordPress as an arbitrary user account, including administrators.

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 WooCommerce Order Proposal plugin for WordPress has a privilege escalation vulnerability in versions up to 2.0.5. The allow_payment_without_login function improperly validates user identity, allowing authenticated Shop Manager-level users to authenticate as any WordPress user, including administrators, by manipulating order proposal requests.

MitigationUpdate the WooCommerce Order Proposal plugin to version 2.0.6 or later, which contains proper permission validation in the allow_payment_without_login function to prevent user impersonation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce Order ProposalWordPress extension
Affected:< 2.0.6

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WooCommerce Order Proposal' by Wpovernight, or check the plugins directory for /wp-content/plugins/woocommerce-order-proposal/
    Affected if Plugin is installed and active
  2. Check installed version
    View the plugin file header at /wp-content/plugins/woocommerce-order-proposal/woocommerce-order-proposal.php or check the plugin admin page for the version number
    Affected if Version is 2.0.5 or lower (below 2.0.6)
  3. Inspect vulnerable function
    Locate and examine the allow_payment_without_login function in the plugin PHP files (typically in main plugin file or includes/class file)
    Affected if Function exists and lacks proper user validation (missing wp_get_current_user() check or nonce validation)
  4. Check for Shop Manager roles
    In WordPress admin under Users > All Users, identify any users with 'Shop Manager' role
    Affected if Shop Manager role users exist and plugin is active
  5. Verify payment endpoint accessibility
    Test if the order proposal payment endpoint (typically /?wc_order_proposal_payment=1 or similar) accepts requests from authenticated Shop Manager sessions without re-authentication
    Affected if Endpoint permits payment without re-prompting for admin-level credentials

User is affected if WooCommerce Order Proposal plugin versions below 2.0.6 are installed and active, with Shop Manager role users present who could exploit the allow_payment_without_login function to impersonate administrators.

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
Upgrade available Upgrade to 2.0.6 or later
Fixed in 2.0.6
Interim mitigation

Update the WooCommerce Order Proposal plugin to version 2.0.6 or later, which contains proper permission validation in the allow_payment_without_login function to prevent user impersonation.

Recommended fix High confidence

2.0.6

  1. Update the WooCommerce Order Proposal plugin to version 2.0.6 or later from the WordPress plugin repository or the vendor's website
  2. Verify the update was successful by checking the installed plugins page in WordPress admin
  3. Confirm the version number reflects 2.0.6 or higher
  4. Review user accounts with Shop Manager roles to ensure no unauthorized access occurred

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

Fix this in Woocommerce Order Proposal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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