CVE-2025-15484
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 · uneditedThe Order Notification for WooCommerce WordPress plugin before 3.6.3 overrides WooCommerce's permission checks to grant full access to all unauthenticated requests, enabling complete read/write access to store resources like products, coupons, and customers.
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 confidenceThe Order Notification for WooCommerce plugin before version 3.6.3 overrides WooCommerce's permission checks, granting full unauthenticated access to all store resources including products, coupons, and customer data. This allows complete read/write access without any authentication.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Order Notification for WooCommerce pluginIn WordPress admin, go to Plugins > Installed Plugins and look for 'Order Notification for WooCommerce' in the list. Note whether it is installed and activated.Affected if The plugin is present and active in the WordPress installation
-
Identify the installed plugin versionClick 'View details' on the Order Notification for WooCommerce plugin in the plugins list, or inspect the plugin header in wp-content/plugins/order-notification-for-woocommerce/order-notification-for-woocommerce.php to find the Version: X.X.X field.Affected if A version number is displayed and it is below 3.6.3
-
Compare version against the vulnerable rangeCompare the installed version found in the previous step to version 3.6.3 using standard version comparison (e.g., 3.6.2 < 3.6.3, 3.6.0 < 3.6.3).Affected if The installed version is any version prior to 3.6.3 (such as 3.6.2, 3.6.1, 3.6.0, or earlier)
If the Order Notification for WooCommerce plugin is installed and running any version before 3.6.3, the environment is affected by this unauthenticated access 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.
dbcve · scopedUpdate the Order Notification for WooCommerce plugin to version 3.6.3 or later to restore proper authentication and permission controls.
Order Notification for WooCommerce version 3.6.3
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate 'Order Notification for WooCommerce' in the plugin list
- If an update is available, click 'Update Now' to install version 3.6.3
- Alternatively, manually upload version 3.6.3 of the plugin via Plugins > Add New > Upload Plugin
- After updating, verify the plugin version shows 3.6.3 in the installed plugins list
- Test that the plugin functionality works correctly with the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-15484 — 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-2025-15484 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