CamPay Shortcode Payment Gateway < 1.7 — Unauthenticated Arbitrary Payment Status Manipulation
CVE-2026-105975Published · Updated Action summary
Affected: <1.7Update to 1.7 or newer
All remediation steps- Severity
- Medium5.3
- CVSS
- 5.3CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:NPrivileges required- None
UI:NUser interaction- None
S:UScope- Unchanged
C:NConfidentiality- None
I:LIntegrity- Low
A:NAvailability- None
- Required access
- No account needed
- Exploit prediction (EPSS)
- 0.2% chance in 30 days15th percentile
- CISA KEV
- Not listed
On this page7
Am I affected?
CamPay Shortcode Payment Gateway campay-shortcode-payment-gateway
- Affected< 1.7
- Patched in1.7
Update to 1.7 or newer.
You are affected if you run < 1.7. Version 1.7 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under CamPay Shortcode 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
- Update to version 1.7, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch CamPay Shortcode Payment Gateway to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence, credited to Pablo González Pérez, Francisco José Ramírez Vicente, Iñigo Sánchez Enciso.
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.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Timeline
CVE published
Severity medium, CVSS 5.3
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.
- EPSS
- Exploit Prediction Scoring System by FIRST.org.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.
