CVE-2026-109962 froxlor CVE debrief

Who should care

Defenders responsible for Froxlor installations, especially those with reseller accounts, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify Froxlor version and API access controls, and ensure that compensating controls are in place for exposed systems.

Why it matters

CVE-2026-109962 is a missing authorization vulnerability in Froxlor versions 0.10.0 before 2.3.14, allowing reseller accounts to read sensitive MySQL server and cronjob configuration via API read commands. Defenders should prioritize verifying and remediating this vulnerability, especially in environments where reseller accounts have access to the Froxlor API.

• Reseller accounts can read sensitive MySQL server and cronjob configuration
• Potential for unauthorized access to management usernames, hosts, ports, TLS settings, and cron metadata
• Requires verification of Froxlor version and API access controls
• Remediation priority for environments with exposed Froxlor installations

Technical summary

The vulnerability allows reseller accounts to read full-admin-only MySQL server and cronjob configuration via API read commands. This is due to a missing authorization check in the MysqlServer and Cronjobs API. The affected product is Froxlor, with versions 0.10.0 before 2.3.14 being vulnerable. The vulnerability has a CVSS score of 5.3 and a severity of MEDIUM. Defenders should prioritize verifying and remediating this vulnerability, especially in environments where reseller accounts have access to the Froxlor API.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability, especially in environments where reseller accounts have access to the Froxlor API.

Recommended defensive actions

• Verify Froxlor version and ensure it is 2.3.14 or later
• Restrict access to the Froxlor API for reseller accounts
• Monitor API activity for suspicious read commands
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details about the vulnerability, including its impact and affected versions. However, additional information from vendor advisories and other sources may be necessary to fully understand the vulnerability and its implications.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.