CVE-2026-130755
Deferred Deferred - Pending Action

Froxlor Authorization Bypass Exposes Traffic Statistics

Vulnerability report for CVE-2026-130755, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: VulnCheck

Description

Froxlor before 2.3.16 contains an authorization bypass vulnerability that allows authenticated customers to read hidden traffic statistics by calling the Traffic.listing API command. Attackers can authenticate to api.php with their API key and secret to retrieve HTTP, FTP, and mail traffic volumes despite the panel.customer_hide_options restriction.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
froxlor froxlor to 2.3.16 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Froxlor before 2.3.16 has an authorization bypass flaw in its Traffic.listing API command. Authenticated customers can exploit this to view hidden traffic statistics (HTTP, FTP, mail) despite administrators hiding the traffic feature via panel.customer_hide_options. The issue occurs because the API does not enforce the traffic restriction, unlike the web interface.

Detection Guidance

Check Froxlor API logs for unauthorized Traffic.listing API calls by authenticated customers. Look for requests to api.php with the Traffic.listing command despite panel.customer_hide_options being enabled. Verify if customers can retrieve HTTP, FTP, or mail traffic statistics when they should be restricted.

Impact Analysis

If you are a Froxlor customer using versions 2.3.15 or earlier, an attacker with your API credentials could access your traffic statistics even if the admin hid this data. This could expose sensitive usage patterns or resource consumption details.

Compliance Impact

This vulnerability may lead to unauthorized access to traffic data, potentially violating data protection requirements under GDPR or HIPAA if the exposed statistics contain personal or sensitive information. Administrators should treat this as a compliance risk.

Mitigation Strategies

Upgrade Froxlor to version 2.3.16 or later if available. If upgrading is not possible, disable the Traffic.listing API command for customers by modifying the API permissions or restricting API access for low-privileged users until a patch is released.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130755. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...