CVE-2026-1305

Japanized for WooCommerce <= 2.8.4 - Missing Authorization to Unauthenticated Paidy Order Manipulation

2026-02-26 21:04
Osvaldo Noe Gonzalez Del Rio (Os)

Strategic Overview

Status
Patched in 2.8.5
Affected Plugin
Japanized for WooCommerce
Affected Version
<= 2.8.4
CVSS
5.3Medium
Weakness type
CWE-287 · Improper Authentication
CVE
CVE-2026-1305
View all Japanized for WooCommerce vulnerabilities

At a glance

CVE-2026-1305 is a medium-severity Improper Authentication vulnerability in the Japanized for WooCommerce WordPress plugin, affecting versions <= 2.8.4. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.5; sites on affected versions should update now. Disclosed February 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).

Vulnerability Overview

The Japanized for WooCommerce plugin for WordPress is vulnerable to Improper Authentication in versions up to, and including, 2.8.4. This is due to a flawed permission check in the `paidy_webhook_permission_check` function that unconditionally returns `true` when the webhook signature header is omitted. This makes it possible for unauthenticated attackers to bypass payment verification and fraudulently mark orders as "Processing" or "Completed" without actual payment via a crafted POST request to the Paidy webhook endpoint.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-287: Improper Authentication

Japanized for WooCommerce <= 2.8.4 carries this weakness at Processing, and reaching it takes no account at all. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.

An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Japanized for WooCommerce the fix is 2.8.5: builds <= 2.8.4 are affected, anything from 2.8.5 onward is not.

Remediation

Update to version 2.8.5, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Japanized for WooCommerce 2.8.5 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1305https://www.wordfence.com/threat-intel/vulnerabilities/id/8cef4b2b-ae8d-4e18-b763-6960a0b944f7https://nvd.nist.gov/vuln/detail/CVE-2026-1305

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C