CamPay Shortcode Payment Gateway < 1.7 - Unauthenticated Arbitrary Payment Status Manipulation
Strategic Overview
- Status
- Patched in 1.7
- Affected Plugin
- CamPay Shortcode Payment Gateway
- Affected Version
< 1.7- CVSS
- 5.3Medium
- Weakness type
- CWE-345 · Insufficient Verification of Data Authenticity
- CVE
CVE-2026-105975
At a glance
CVE-2026-105975 is a medium-severity Insufficient Verification of Data Authenticity vulnerability in the CamPay Shortcode Payment Gateway WordPress plugin, affecting versions < 1.7. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.7; sites on affected versions should update now. Disclosed October 2026, reported by Pablo González Pérez.
Vulnerability Overview
The CamPay Shortcode Payment Gateway plugin for WordPress is vulnerable to Insufficient Verification of Data Authenticity in all versions up to 1.7. This is due to missing server-side verification of payment status in the validate_payment() callback handler, which accepted the payment outcome directly from client-supplied GET parameters without verifying the response against the CamPay API or validating a cryptographic signature. This makes it possible for unauthenticated attackers to unauthenticated attackers to mark arbitrary payment records as paid, corrupt genuine payment records, and write post meta onto arbitrary post IDs by supplying a forged status value in the callback URL.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-345: Insufficient Verification of Data Authenticity
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
Remediation
Update to version 1.7, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: CamPay Shortcode Payment Gateway 1.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C