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

> Unauthenticated attackers can forge payment statuses and modify arbitrary post metadata by manipulating client-supplied parameters in the CamPay Shortcode Payment Gateway plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-59h8-hqv9-9m63

## What is CVE-2026-105975?

CVE-2026-105975 is a medium-severity vulnerability in Unknown CamPay Shortcode Payment Gateway, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-105975?


## How do I fix CVE-2026-105975?

No fix has been published for CVE-2026-105975 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-105975 being exploited?

There is no known exploitation of CVE-2026-105975 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105975 and fix it if it is affected.

What it is: CVE-2026-105975 is a medium-severity vulnerability in Unknown CamPay Shortcode Payment Gateway, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105975 in the wild and no public exploit code.

Affected product: Unknown CamPay Shortcode Payment Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105975/ (Markdown: https://insights.sbomify.com/CVE-2026-105975/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105975
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105975
- OSV: https://osv.dev/vulnerability/CVE-2026-105975

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105975/
Summaries are generated and may contain mistakes; the official description above is the record.