CVE-2025-15475Public exploitNetwork attack vectorHinoki check available

Unauthenticated order-status modification via unverified callback signature

Published Jan 14, 2026 · Updated Jan 14, 2026

Missing authorization in PayHere Payment Gateway 2.3.9 and earlier allows remote attackers to alter pending WooCommerce order status. The check_payhere_response callback accepts attacker-controlled payment fields without validating md5sig against a merchant-secret-derived value before setting the order to paid, completed, or on hold. No account or user interaction is required; the bounded impact is unauthorized order-state modification rather than data disclosure or service interruption.

CVSS severity5.3
Medium
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Missing authorization in PayHere Payment Gateway 2.3.9 and earlier allows remote attackers to alter pending WooCommerce order status. The check_payhere_response callback accepts attacker-controlled payment fields without validating md5sig against a merchant-secret-derived value before setting the order to paid, completed, or on hold. No account or user interaction is required; the bounded impact is unauthorized order-state modification rather than data disclosure or service interruption.

The record

CVE
CVE-2025-15475
Published
Jan 14, 2026
Updated
Jan 14, 2026
Vendor
PayHere
Product
PayHere Payment Gateway
Classifications
CWE-862, T1190
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jan 14, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 14, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=* <=2.3.9

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

PayHere · PayHere Payment Gatewayversion=* <=2.3.9

Published CVSS scores

5.3WordfenceCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-862Missing Authorization
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo