CVE-2023-1033: Froxlor Cross-Site Request Forgery vulnerability
8.8
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.50212%
CWE
Published
2/25/2023
Updated
3/7/2023
KEV Status
No
Technology
PHP
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| froxlor/froxlor | composer | < 2.0.11 | 2.0.11 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from state-changing AJAX endpoints (updateTablelisting and resetTablelisting) using Request::any() to retrieve parameters. This allowed requests via any HTTP method (including GET), bypassing CSRF protections. The patch replaced Request::any() with Request::post(), enforcing POST method usage. Since POST requests require explicit user interaction (e.g., form submission) and are typically paired with CSRF tokens in frameworks, this change mitigates CSRF by preventing trivial exploitation via GET. The absence of CSRF token checks in the original code further exacerbated the issue, making these functions high-confidence candidates.