VulnCrest
Search
Create account
Report an incident
Radar sectionsDatabase
Check my site
WordPress plugin

PayHere Payment Gateway Plugin for WooCommerce <= 2.3.9 — Missing Authorization to Unauthenticated Order Status Modification

CVE-2025-15475Published · Updated

Action summary

Affected: ≤2.3.9Update to 2.4.0 or newer

All remediation steps
Watch plugin
Severity
Medium5.3
CVSS
5.3
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:U Scope
Unchanged
C:N Confidentiality
None
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-862 Missing Authorization
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed
On this page8

Am I affected?

PayHere Payment Gateway payhere-payment-gateway

  1. Affected≤ 2.3.9
  2. Patched in2.4.0

Update to 2.4.0 or newer.

You are affected if you run ≤ 2.3.9. Version 2.4.0 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under PayHere Payment Gateway.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 2.4.0, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch PayHere Payment Gateway to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Md. Moniruzzaman Prodhan (NomanProdhan).

The PayHere Payment Gateway Plugin for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to an improper validation logic in the check_payhere_response function in all versions up to, and including, 2.3.9. This makes it possible for unauthenticated attackers to change the status of pending WooCommerce orders to paid/completed/on hold.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in PayHere Payment Gateway

All 3
More vulnerabilities in PayHere Payment Gateway
SeverityVulnerabilityCVEPublished
Medium5.32.4.5 - Unauthenticated Payment Bypass
2.4.0 – 2.4.5No patch available
CVE-2026-103310
Medium5.3Information Disclosure via Log Files
≤2.2.11Update to 2.2.12
CVE-2023-6064

Same weakness (Missing Authorization)

All Missing Authorization
Other Missing Authorization vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup≤5.25.25Update to 5.26.45
CVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder≤1.0.2Update to 1.1
CVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System≤3.3.9Update to 3.4.0
CVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity medium, CVSS 5.3

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
CVE® identifiers
Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Jump to

Are you sure?