Security readout for executives and security teams
Plain-English summary
CVE-2026-1305 affects the Japanized for WooCommerce WordPress plugin. An unauthenticated attacker may be able to make unpaid orders appear as Processing or Completed when the Paidy payment webhook is exposed. Business impact is potential order fraud, not server takeover. Public sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term e-commerce fraud risk. Prioritize stores accepting Paidy payments through this plugin. Patch or disable affected payment handling after validating operational impact. This is not described as data theft or system compromise in the provided sources.
Technical view
Versions up to and including 2.8.4 have improper authentication in paidy_webhook_permission_check. If the webhook signature header is omitted, the check returns true, allowing unauthenticated POST requests to bypass Paidy payment verification and change order status. The issue is tracked as CWE-287 with CVSS 3.1 score 5.3.
Likely exposure
Exposure is likely limited to WordPress/WooCommerce sites using Japanized for WooCommerce <= 2.8.4 with the Paidy payment integration or webhook endpoint reachable from the internet. Sites not using this plugin or Paidy flow are less likely to be affected.
Exploitation context
The issue is remotely reachable and requires no login, no user interaction, and low attack complexity. The known impact is order integrity manipulation. KEV is false, and the provided sources do not report active exploitation in the wild.
Researcher notes
The source bundle states <=2.8.4 is vulnerable, but the affected metadata is sparse and lists defaultStatus as unaffected. Wordfence, CVE, code references, and a WordPress Trac changeset support the authentication flaw and remediation direction. No exploit code or confirmed exploitation is cited.
Mitigation direction
- Inventory WordPress sites for Japanized for WooCommerce and installed version.
- Update to a version newer than 2.8.4 if available from official sources.
- Review vendor and WordPress plugin guidance for the referenced changeset or release notes.
- Temporarily disable Paidy payment handling if business impact allows and no fix is available.
- Monitor orders for unpaid transactions marked Processing or Completed.
Validation and detection
- Confirm whether Japanized for WooCommerce is installed and active.
- Check whether the installed version is 2.8.4 or earlier.
- Verify whether Paidy payment gateway functionality is enabled.
- Review recent Paidy orders against settlement records.
- Compare installed plugin code with the referenced WordPress Trac changeset.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1305 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/8cef4b2b-ae8d-4e18-b763-6960a0b944f7?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/woocommerce-for-japan/trunk/includes/gateways/paidy/class-wc-paidy-endpoint.php#L63CVE reference
- https://plugins.trac.wordpress.org/browser/woocommerce-for-japan/tags/2.8.2/includes/gateways/paidy/class-wc-paidy-endpoint.php#L108CVE reference
- https://plugins.trac.wordpress.org/changeset/3464868/woocommerce-for-japan/trunk/includes/gateways/paidy/class-wc-paidy-endpoint.phpCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.