Description
The PayHere Payment Gateway WordPress plugin from 2.4.0 through 2.4.5 does not verify the authenticity of payment notifications when the merchant secret is unset, which is the default state, allowing unauthenticated attackers to forge a payment confirmation and mark any order as paid without payment.
Published: 2026-11-02
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: Unauthorized Payment Confirmation
Action: Patch
AI Analysis

Impact

The PayHere Payment Gateway WordPress plugin in versions 2.4.0 through 2.4.5 accepts payment notifications without verifying their authenticity when the merchant secret is not configured, which is the default. An attacker who can reach the notification endpoint can forge a payment confirmation and mark any order as paid without having actually paid. This results in fraudulent revenue for the merchant, undermining financial integrity. The flaw is a form of improper input validation of payment data, allowing unauthorized transaction approvals.

Affected Systems

This vulnerability is present in the PayHere Payment Gateway WordPress plugin for versions 2.4.0 to 2.4.5. The affected vendor is PayHere Payment Gateway and any WordPress site that has installed this plugin within those versions.

Risk and Exploitability

The CVSS score is 5.3, indicating a moderate severity. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires that the plugin is installed and the merchant secret remains unset, which is the default configuration. Attackers can directly target the payment notification endpoint and forge confirmations without authentication, potentially generating fraudulent orders. Monitor deployments for this default state and apply updates or configuration changes promptly.

Generated by OpenCVE AI on November 2, 2026 at 08:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Install the latest PayHere Payment Gateway plugin release that includes merchant secret verification.
  • Configure the plugin with a non‑empty merchant secret, enabling authentication checks for payment notifications.
  • If an update or configuration change cannot be applied immediately, block or disable the payment notification endpoint until proper authentication is enforced.

Generated by OpenCVE AI on November 2, 2026 at 08:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 02 Nov 2026 08:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-20
CWE-613

Mon, 02 Nov 2026 07:30:00 +0000

Type Values Removed Values Added
Description The PayHere Payment Gateway WordPress plugin from 2.4.0 through 2.4.5 does not verify the authenticity of payment notifications when the merchant secret is unset, which is the default state, allowing unauthenticated attackers to forge a payment confirmation and mark any order as paid without payment.
Title PayHere Payment Gateway 2.4.0 - 2.4.5 - Unauthenticated Payment Bypass via Unverified Payment Notification
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-11-02T07:10:35.208Z

Reserved: 2026-09-30T11:37:26.685Z

Link: CVE-2026-103310

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-02T08:17:35.927

Modified: 2026-11-02T08:17:35.927

Link: CVE-2026-103310

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-02T08:30:07Z

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-613

    Insufficient Session Expiration