Quick answers
- Is CVE-2026-100719 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100719 being exploited in the wild.
- How severe is CVE-2026-100719?
- Medium severity, with a CVSS score of 6.5, published 26 September 2026.
- Which products and versions are affected?
- Froxlor before 2.3.12.
- Is there a fix for CVE-2026-100719?
- A patch was published on 2026-09-06: patch version 2.3.12 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100719 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100719?
- Check whether you run Froxlor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a sensitive information disclosure in the DirProtections API endpoint that fails to redact the password field containing htpasswd bcrypt hashes from serialized responses. An authenticated attacker with API credentials can call DirProtections.listing to retrieve password hashes, which can be cracked offline or used to identify credential reuse. The issue affects versions before 2.3.12 and is fixed by redacting credential fields from API serializers.
Affected products
- Froxlor Froxlor before 2.3.12
Timeline
- 2026-09-26: disclosed
- 2026-09-06: patched: patch version 2.3.12 released