# CVE-2026-124624: PipraPay pp-token anti-CSRF pp-adapter.php hash_hmac hard-coded credentials


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-47g8-2fh9-8w47

## What is CVE-2026-124624?

CVE-2026-124624 is a medium-severity vulnerability in PipraPay, published on 9 Nov 2026. 

### Official description

A weakness has been identified in PipraPay 3.0.0. Affected by this vulnerability is the function hash_hmac of the file pp-content/pp-include/pp-adapter.php of the component pp-token anti-CSRF Handler. Executing a manipulation can lead to hard-coded credentials. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2026-124624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124624 is a medium-severity vulnerability in PipraPay, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124624 in the wild and no public exploit code.

Affected product: PipraPay. 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-124624/ (Markdown: https://insights.sbomify.com/CVE-2026-124624/index.md)
```

## Sources

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

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