Unauthorized settings changes via forged listing requests
Published Feb 25, 2023 · Updated Mar 11, 2025
Cross-site request forgery in Froxlor before 2.0.11 allows remote attackers to alter an authenticated user's table-listing settings. The updateTablelisting and resetTablelisting AJAX handlers accept GET-or-POST parameters through Request::any, while Listing::storeColumnListingForUser stores unchecked section and column names. Exploitation requires an authenticated user to load an attacker-controlled request; the demonstrated consequence is unauthorized modification of that user's saved interface state.
Summary
What happened
Cross-site request forgery in Froxlor before 2.0.11 allows remote attackers to alter an authenticated user's table-listing settings. The updateTablelisting and resetTablelisting AJAX handlers accept GET-or-POST parameters through Request::any, while Listing::storeColumnListingForUser stores unchecked section and column names. Exploitation requires an authenticated user to load an attacker-controlled request; the demonstrated consequence is unauthorized modification of that user's saved interface state.
The record
- CVE
- CVE-2023-1033
- Published
- Feb 25, 2023
- Updated
- Mar 11, 2025
- Vendor
- Froxlor
- Product
- Froxlor
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2023CVE publishedPublication date reported by the CVE source.
- Mar 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.0.11
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- huntr Froxlor CSRF proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo