Skip to main content

Cfx.re FXServer CVE-2024-46310

CRITICAL
Improper Preservation of Permissions (CWE-281)
2025-01-13 cve@mitre.org
9.1
CVSS 3.1 · Vendor: mitre
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Permission preservation
Impact

CVSS 9.1, EPSS 83.0%. FiveM has millions of active players across thousands of community servers. Server operators often store player financial data (in-game currencies), personal information, and Discord account links. The gaming server ecosystem is actively targeted by griefers and data harvesters.

Exploit ScenarioDerived

An attacker discovers an FXServer instance and queries the unauthenticated API to enumerate all registered players. They modify player data to grant themselves administrator privileges, then use the admin functions to execute Lua scripts on the server. They exfiltrate the player database and ransom it back to the server operator.

Emergency Immediate action required. Why: CRITICAL + EPSS > 30%, no patch available.
No patch listed yet 83.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 28, 2026

Cfx.re FXServer (FiveM/RedM game server framework) version 9601 and earlier exposes unauthenticated API endpoints that allow reading and modifying arbitrary user data. Attackers can enumerate player information, modify account details, and access server administration functions without any credentials.

Earlier versions of this analysis (1)
v1 Mar 28, 2026 - 18:03 CVSS 9.1

Unauthenticated API access in FXServer allows arbitrary user data manipulation and server configuration changes in FiveM/RedM game servers.

RemediationAI

Update FXServer to a version later than v9601. Implement authentication on all API endpoints. Restrict API access to trusted IP addresses. Deploy a reverse proxy with rate limiting in front of the FXServer API. Monitor API access logs for unauthorized enumeration patterns.

Affected ProductsAI

Cfx.re FXServer <= v9601 FiveM servers RedM servers

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FXServer powers the FiveM (GTA V) and RedM (Red Dead Redemption 2) multiplayer modification frameworks. The REST API endpoints used for server management and player data lack authentication checks. An attacker can directly call these endpoints to read player profiles, modify user data, alter server configurations, and potentially execute server-side scripts.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Primary rating from Vendor (mitre) · only source for this CVE.

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

DescriptionCVE.org

Incorrect Access Control in Cfx.re FXServer v9601 and earlier allows unauthenticated users to modify and read arbitrary user data via exposed API endpoint

Executive ViewAI

Why It Matters

Organizations using Cfx.re FXServer face critical risk from CVE-2024-46310 rated CVSS 9.1. Successful exploitation could critically impact the confidentiality, integrity, and availability of affected systems. With an EPSS score of 83%, this vulnerability faces very high likelihood of exploitation. Organizations should apply vendor updates immediately when available and implement compensating controls in the interim.

Business Impact: Severe
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Implement network-level access controls to limit exposure; (2) Enable enhanced monitoring and alerting; (3) Apply principle of least privilege.

Threat Intelligence Overview

Threat Score
5.8/10
Composite threat intelligence
EPSS Score
83.0%
Top 1% exploitable
Exploit
POC
Public exploit code exists
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS 83.0%
Patch available No
Active threat Yes
Deciding rule
CRITICAL + EPSS > 30%, no patch available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

149
Low Medium High Critical
KEV: 0
EPSS: +83
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy