CVE-2025-59843
BaseFortify
Publication date: 2025-09-26
Last updated on: 2025-10-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| flagforge | flagforge | From 2.0 (inc) to 2.3.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-359 | The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Flag Forge versions 2.0.0 to before 2.3.1 causes the public API endpoint /api/user/[username] to expose user email addresses in its JSON response. This means anyone accessing this endpoint could retrieve email addresses of users, potentially compromising user privacy. The issue was fixed in version 2.3.1 by removing email addresses from the public API response while keeping the endpoint accessible.
How can this vulnerability impact me? :
The vulnerability can lead to exposure of user email addresses to unauthorized parties, which may result in privacy breaches, increased risk of phishing attacks, spam, or other malicious activities targeting users. It compromises the confidentiality of user information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
Exposing user email addresses publicly without consent can violate privacy requirements under regulations such as GDPR and HIPAA, which mandate protection of personally identifiable information. This vulnerability could lead to non-compliance due to unauthorized disclosure of personal data.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Flag Forge to version 2.3.1 or later, as this version removes email addresses from the public API responses. There are no workarounds for this vulnerability.