VulnerabilityPublished 2 Oct 2024

CVE-2024-41290: CVE-2024-41290 · Cleartext Storage of Sensitive Information in a Cookie

Affects CVE-2024-41290Source CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.1High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 2 Oct 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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
GitHubparagbagul111/CVE-2024-41290`pkg:github/paragbagul111/CVE-2024-41290`Other threats	Affected =1.3.1	Fixed in–

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

AI-suggested

Until an official patch is released, organizations should implement specific mitigations to reduce risk. First, review and restrict network access to the FlatPress CMS administration interface, limiting it to trusted IP addresses or VPNs to reduce exposure. Enable HTTPS to protect cookie transmission and prevent interception. Investigate the possibility of configuring cookies with secure attributes such as HttpOnly and Secure flags to mitigate theft via client-side scripts or network sniffing. Consider implementing additional authentication layers like multi-factor authentication (MFA) to reduce the impact of compromised credentials. Regularly monitor CMS logs for suspicious login activity or session anomalies. If feasible, temporarily disable or restrict cookie-based authentication and switch to alternative authentication mechanisms. Educate users and administrators about the vulnerability and encourage prompt password changes if compromise is suspected. Maintain up-to-date backups of CMS content to enable recovery in case of compromise. Finally, track FlatPress CMS vendor communications for forthcoming patches and apply them immediately upon release.

Description

FlatPress CMS v1.3.1 1.3 was discovered to use insecure methods to store authentication data via the cookie's component.

Impact

The impact of CVE-2024-41290 is significant for organizations using FlatPress CMS version 1.3.1. Exploitation can lead to unauthorized disclosure of authentication credentials, enabling attackers to hijack user sessions or escalate privileges within the CMS. This compromises the confidentiality and integrity of user accounts and potentially the entire content management system. Attackers could manipulate website content, deface pages, or inject malicious code, affecting the organization's reputation and user trust. Since the vulnerability does not affect availability, denial-of-service is less likely; however, the breach of authentication data can lead to broader security incidents. Organizations relying on FlatPress CMS for critical web services or customer-facing portals are at higher risk. The vulnerability's ease of exploitation (low complexity, no user interaction) increases the likelihood of attacks once exploit code becomes available. Without patches, organizations face prolonged exposure, increasing the window for potential compromise. The absence of known exploits currently provides a limited window for proactive mitigation before active attacks emerge.

CWE-315Cleartext Storage of Sensitive Information in a Cookie (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product stores sensitive information in cleartext in a cookie.
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
Attack patterns
Accessing/Intercepting/Modifying HTTP Cookies (opens in a new tab)
Retrieve Embedded Sensitive Data (opens in a new tab)
Manipulating Opaque Client-based Data Tokens (opens in a new tab)
Manipulating State (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/paragbagul111/CVE-2024-41290 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 06:57 UTC

WeaknessesCWE-315

Technical details

References

Community reviews

Related threats