CVE-2024-35539VulnerabilityPublished 19 Aug 2024Updated 21 Aug 2024

CVE-2024-35539: n/a

Source CVE Database V5

Not known to be exploited · public exploit available (Exploit-DB) · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

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

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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 19 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
1 Exploit-DB entry, 234 days after disclosure
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

CVE ID reserved
by mitre
2024-05-17, 94 days before disclosure
CVE published
on cve.org
2024-08-19, t = 0
First Exploit-DB entry (opens in a new tab)
Typecho 1.3.0 - Race Condition
2025-04-10, 234 days after disclosure

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 2026-10-26.

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

AI-suggested

Until an official patch is released, organizations should implement specific mitigations to reduce the risk of exploitation. These include: 1) Implementing server-side rate limiting on comment submissions to restrict the number of comments accepted from a single IP address or user within a short timeframe, effectively reducing the window for race condition exploitation. 2) Enabling or enhancing manual or automated comment moderation to detect and filter spam comments that bypass frequency checks. 3) Temporarily disabling the comment feature if feasible, especially on high-traffic or sensitive sites, to eliminate the attack vector. 4) Employing web application firewalls (WAFs) with custom rules to detect and block rapid multiple comment submissions indicative of race condition exploitation. 5) Monitoring logs for unusual comment activity patterns to identify potential exploitation attempts early. 6) Engaging with the Typecho community or developers to track patch releases and apply updates promptly once available. These targeted mitigations go beyond generic advice by focusing on controlling comment submission rates and enhancing detection capabilities specific to this race condition vulnerability.

Description

Typecho v1.3.0 was discovered to contain a race condition vulnerability in the post commenting function. This vulnerability allows attackers to post several comments before the spam protection checks if the comments are posted too frequently.

Impact

The primary impact of CVE-2024-35539 is on the integrity and availability of the comment system within Typecho-based websites. Attackers can exploit the race condition to post multiple comments rapidly, bypassing spam protections. This can lead to comment spam flooding, degrading user experience and potentially overwhelming backend resources, which may cause denial of service conditions or increased operational costs due to moderation overhead. While confidentiality is not directly affected, the integrity of user-generated content is compromised, which can damage the reputation of affected websites. For organizations relying on Typecho for community engagement or content management, this vulnerability can disrupt normal operations and reduce trust in the platform. Since no authentication is required, the attack surface is broad, increasing the likelihood of exploitation once public awareness grows. The absence of known exploits currently limits immediate risk, but the medium severity rating indicates a meaningful threat that should be addressed proactively.

Summary

CVE-2024-35539 is a race condition vulnerability identified in the post commenting functionality of Typecho version 1.3.0, a lightweight blogging platform. The flaw arises because the spam protection mechanism, which limits comment posting frequency, does not effectively synchronize concurrent comment submissions. Attackers can exploit this race condition by submitting multiple comments in rapid succession, bypassing the frequency checks that are intended to prevent spam. This vulnerability does not require any authentication or user interaction, making it remotely exploitable over the network with low complexity. The consequence is that attackers can flood comment sections with spam or malicious content, potentially degrading the integrity of the comment system and impacting availability by overwhelming the comment processing system. The CVSS 3.1 score of 6.5 reflects these factors: network attack vector, low attack complexity, no privileges or user interaction required, and impacts on integrity and availability but not confidentiality. No patches or official fixes have been released at the time of this report, and no known exploits have been observed in the wild. The vulnerability is classified under CWE-290 (Authentication Bypass by Spoofing), indicating that the spam protection mechanism is effectively bypassed due to the race condition. Organizations using Typecho should be aware of this issue and consider interim controls such as enhanced rate limiting, comment moderation, or disabling comments temporarily until a patch is available.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Description

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

Public exploits and detection1 Exploit-DB entry

WeaknessesCWE-290

Technical details

References

Community reviews

Related threats