EUVD-2026-52997
GHSA-4q74-w4p3-c8cx
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CSRF requires no attacker privileges (PR:N) but mandates victim interaction (UI:R); impact is integrity-only at low level (I:L) with no confidentiality or availability consequences and no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A security vulnerability has been detected in RackTables up to 0.22.0/e5fff9f8aab339798ed47e8c6d7d977ed97a82bd. This vulnerability affects unknown code. The manipulation leads to cross-site request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The project maintainer confirms: "[I]t seems plausible, in that RackTables does not at this time have any CSRF prevention. You may assign a CVE ID to this, but there is no guarantee it will be handled in urgent, or even timely, manner, or at all."
AnalysisAI
Cross-site request forgery in RackTables through version 0.22.0 enables remote attackers to perform unauthorized state-changing actions against authenticated users' sessions by enticing them to visit attacker-controlled pages. The project maintainer has publicly confirmed the complete absence of any CSRF protection across the entire codebase and has explicitly declined to commit to a timely fix, making this a persistent, unfixed exposure. A public POC exists on GitHub; however, no active exploitation is confirmed in CISA KEV, and the CVSS 4.0 score of 2.1 reflects the limited integrity-only impact and mandatory user interaction requirement.
Technical ContextAI
RackTables is an open-source web-based datacenter asset management and rack documentation tool. CWE-352 (Cross-Site Request Forgery) arises when a web application processes state-changing HTTP requests without verifying they originate from the legitimate authenticated session rather than a third-party origin. The maintainer's own statement confirms no CSRF tokens, SameSite cookie enforcement, or equivalent origin-validation mechanisms exist anywhere in RackTables. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P) indicates the application is network-accessible with no special attack prerequisites, but requires passive user interaction - the victim must navigate to an attacker-controlled page while holding an active RackTables session. CPE identifier cpe:2.3:a:n/a:racktables:*:*:*:*:*:*:*:* covers all versions without restriction.
RemediationAI
No vendor-released patch has been identified at time of analysis; the project maintainer explicitly stated there is no guarantee the issue will be addressed urgently or at all. Primary compensating control: restrict RackTables web interface access to trusted internal networks or VPN-only segments, which eliminates cross-origin CSRF attack paths from external attacker-controlled pages - trade-off is reduced accessibility for remote administrators. Secondary control: deploy a reverse proxy or WAF with CSRF protection capabilities (e.g., ModSecurity with OWASP CRS) in front of RackTables to inject and validate CSRF tokens transparently - trade-off is added infrastructure complexity and potential false positives on legitimate requests. Additionally, enforce short session timeouts in the RackTables configuration to minimize the window during which a valid session can be abused. Advise authenticated users to avoid browsing untrusted sites during active RackTables sessions. The researcher advisory and POC are documented at https://github.com/fa1c4/security-advisories/blob/main/RackTables/RackTables_CSRF_report.md.
More in Racktables
View allSame weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today