VulnerabilityPublished 17 Nov 2024Updated 18 Nov 2024

CVE-2024-52872: flagsmith

Affects flagsmithSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 2.134.1 soon.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.134.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade flagsmith/flagsmith to 2.134.1.

Affected software

Product	Affected	Fixed in
GitHubflagsmith/flagsmith`pkg:github/flagsmith/flagsmith`Other threats	Affected <2.134.1	Fixed in 2.134.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-52872, organizations should immediately upgrade Flagsmith to version 2.134.1 or later, where the get_document endpoint is properly protected by permissions. Until patching is complete, restrict network access to the Flagsmith API endpoints using firewalls or network segmentation to limit exposure to trusted internal users only. Implement monitoring and alerting for unusual access patterns to the get_document endpoint to detect potential exploitation attempts. Review and audit access control policies and logs to ensure no unauthorized document retrieval has occurred. Additionally, consider applying Web Application Firewall (WAF) rules to block suspicious requests targeting this endpoint. Educate development and security teams about the importance of enforcing strict access controls on API endpoints to prevent similar vulnerabilities in the future.

Description

In Flagsmith before 2.134.1, the get_document endpoint is not correctly protected by permissions.

Impact

The primary impact of CVE-2024-52872 is unauthorized disclosure of sensitive information stored or accessible via the get_document endpoint in Flagsmith. This can lead to leakage of confidential business data, internal configurations, or proprietary documents, potentially aiding further attacks or corporate espionage. Since integrity and availability are unaffected, the threat mainly concerns confidentiality breaches. Organizations using vulnerable Flagsmith versions expose themselves to remote attackers who can exploit this flaw without any authentication or user interaction, increasing the attack surface significantly. The ease of exploitation combined with the potential sensitivity of exposed data can result in reputational damage, regulatory compliance violations, and financial losses. The absence of known exploits in the wild currently reduces immediate risk, but the vulnerability’s characteristics make it a likely target for attackers once publicized.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 03:07 UTC

Technical details

References

Community reviews

Related threats