dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14886

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-09
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 Japanized for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `order` REST API endpoint in all versions up to, and including, 2.7.17. This makes it possible for unauthenticated attackers to mark any WooCommerce order as processed/completed.

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 Japanized for WooCommerce plugin for WordPress has a broken access control vulnerability in its order REST API endpoint. The endpoint lacks capability checks, allowing unauthenticated attackers to send requests that mark any WooCommerce order as processed or completed without proper authorization.

MitigationUpdate the Japanized for WooCommerce plugin to version 2.7.18 or later, which includes proper capability checks on the order REST API endpoint. Until then, consider disabling or restricting the affected REST API endpoint at the server level.

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. Confirm Japanized for WooCommerce is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Japanized for WooCommerce' in the list. Note the version number displayed below the plugin name.
    Affected if The plugin is active and the version is below 2.7.18 or the version cannot be determined
  2. Retrieve plugin version via WP-CLI
    Run command: wp plugin list --plugin='japanized-for-woocommerce' --format=table or inspect the plugin main file header at /wp-content/plugins/woocommerce-jp/.
    Affected if The displayed version is lower than 2.7.18
  3. Verify WooCommerce is active
    In WordPress admin, go to Plugins and confirm WooCommerce is installed and active. The vulnerability requires WooCommerce to be present.
    Affected if WooCommerce is active alongside a vulnerable version of Japanized for WooCommerce
  4. Test unauthenticated REST API access
    Send a GET or POST request to /wp-json/wc-jp/v1/orders or the plugin's order endpoint without providing authentication credentials. Use a tool like curl: curl -s -X POST https://yourdomain.com/wp-json/wc-jp/v1/orders -H 'Content-Type: application/json' -d '{"id":1,"status":"completed"}'.
    Affected if The endpoint responds with success or allows order status modification without returning a 401/403 authentication error

A user is affected if the Japanized for WooCommerce plugin is installed with a version earlier than 2.7.18 and the REST API endpoint is accessible without authentication, allowing unauthorized order status changes.

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 the Japanized for WooCommerce plugin to version 2.7.18 or later, which includes proper capability checks on the order REST API endpoint. Until then, consider disabling or restricting the affected REST API endpoint at the server level.

Recommended fix Moderate confidence

Version higher than 2.7.18 (check WordPress plugin repository for latest stable release)

  1. Update the Japanized for WooCommerce plugin to the latest available version from the WordPress plugin repository
  2. After updating, verify that the order status can only be modified by authenticated users with appropriate capabilities
  3. Test that WooCommerce order status changes require proper authorization

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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