CVE-2024-52872: n/a
In Flagsmith before 2.134.1, the get_document endpoint is not correctly protected by permissions.
AI Analysis
Technical Summary
CVE-2024-52872 identifies a security vulnerability in the Flagsmith feature flag management platform, specifically affecting versions before 2.134.1. The vulnerability arises because the get_document API endpoint does not enforce proper permission checks, allowing any remote attacker to retrieve documents without authentication or user interaction. The CVSS v3.1 score of 7.5 (high) reflects the ease of exploitation (network accessible, no privileges required) and the impact on confidentiality, as sensitive information can be disclosed. There is no impact on integrity or availability. The vulnerability is classified as a broken access control issue, where the endpoint's access control mechanisms are either missing or improperly implemented. Although no known exploits have been reported in the wild, the straightforward nature of the flaw makes it a significant risk for organizations relying on Flagsmith for feature flag management. The lack of authentication and user interaction requirements means attackers can automate exploitation remotely, potentially harvesting sensitive documents or configuration data. The vulnerability was published on November 17, 2024, and the recommended fix is to upgrade to Flagsmith version 2.134.1 or later, where proper permission checks are enforced on the get_document endpoint.
Potential 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.
Mitigation Recommendations
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.
Affected Countries
United States, United Kingdom, Germany, Canada, Australia, Netherlands, France, India, Japan, Singapore
CVE-2024-52872: n/a
Description
In Flagsmith before 2.134.1, the get_document endpoint is not correctly protected by permissions.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2024-52872 identifies a security vulnerability in the Flagsmith feature flag management platform, specifically affecting versions before 2.134.1. The vulnerability arises because the get_document API endpoint does not enforce proper permission checks, allowing any remote attacker to retrieve documents without authentication or user interaction. The CVSS v3.1 score of 7.5 (high) reflects the ease of exploitation (network accessible, no privileges required) and the impact on confidentiality, as sensitive information can be disclosed. There is no impact on integrity or availability. The vulnerability is classified as a broken access control issue, where the endpoint's access control mechanisms are either missing or improperly implemented. Although no known exploits have been reported in the wild, the straightforward nature of the flaw makes it a significant risk for organizations relying on Flagsmith for feature flag management. The lack of authentication and user interaction requirements means attackers can automate exploitation remotely, potentially harvesting sensitive documents or configuration data. The vulnerability was published on November 17, 2024, and the recommended fix is to upgrade to Flagsmith version 2.134.1 or later, where proper permission checks are enforced on the get_document endpoint.
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2024-11-17T00:00:00.000Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 699f6bbab7ef31ef0b55a6eb
Added to database: 2/25/2026, 9:38:02 PM
Last enriched: 2/28/2026, 3:07:00 AM
Last updated: 4/12/2026, 7:53:02 AM
Views: 20
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.