PayHere Payment Gateway 2.4.0 - 2.4.5 - Unauthenticated Payment Bypass via Unverified Payment Notification
Only PayHere Payment Gateway WordPress plugin versions 2.4.0 through 2.4.5 are listed, and the flaw applies when the merchant secret is unset, the default state. No vendor rating or fix is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 35/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The PayHere Payment Gateway plugin for WordPress is affected by this vulnerability. An unauthenticated attacker can send forged payment notifications to mark orders as paid without actually making a payment, because the plugin does not verify notification authenticity when the merchant secret is not set, which is its default configuration.
Read the original 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.
What to do
Check every install: default setups are affected.
Workaround: The facts give no vendor workaround. Because the issue applies only when the merchant secret is unset, setting a merchant secret is the condition the sources point to while no fix exists.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Unknown PayHere Payment Gateway
From 2.4.0 · through 2.4.5
Evidence 1
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-103310
What does this mean?
The plugin accepts a payment confirmation that has not been verified. An unauthenticated attacker can forge that confirmation and mark any order as paid without payment.Source: wpscan.com
Am I affected, and how do I check?
The listed range is PayHere Payment Gateway versions 2.4.0 through 2.4.5 of the WordPress plugin, and the issue applies when the merchant secret is unset, which is the default. To check, look up the installed plugin version and confirm whether a merchant secret has been set in the plugin's settings.Source: wpscan.com
What should I do about it?
The checked facts list no fixed version, so no upgrade target is given. Check whether your installed version falls within 2.4.0 through 2.4.5 and watch for a vendor release that names a fixed version.Source: wpscan.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The facts give no vendor workaround. Because the issue applies only when the merchant secret is unset, setting a merchant secret is the condition the sources point to while no fix exists.Source: wpscan.com