Skip to main content
VulnerabilityPublished

CVE-2026-100711: froxlor versions before 2.3.12 fail to invalidate existing panel sessions, API keys, and 2FA trust cookies when a user password is changed

Affects froxlorSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.3.12 soon.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.3.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

What to do

Upgrade froxlor/froxlor to 2.3.12.

Affected software

ProductAffectedFixed in
GitHubfroxlor/froxlorpkg:github/froxlor/froxlorOther threatsAffected
  • <2.3.12
Fixed in
  • 2.3.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade froxlor to version 2.3.12 or later, where this issue is fixed. Versions before 2.3.12 are vulnerable because they do not invalidate sessions, API keys, and 2FA trust cookies upon password change. No vendor advisory or patch link is provided here, but the version 2.3.12 is explicitly stated as the fixed version.

Description

froxlor versions before 2.3.12 do not invalidate existing panel sessions, API keys, and 2FA trust cookies when a user changes their password. This allows attackers who have hijacked sessions or possess valid API keys or 2FA trust tokens to maintain full account access even after password rotation, effectively bypassing incident response measures.

References

Community reviews

Loading reviews…