VulnerabilityPublished 1 Jun 2025

CVE-2025-5404: chaitak-gorai Blogbook · Denial of Service

Affects chaitak-gorai BlogbookSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 4.0 base score

5.3Medium

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

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

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Jun 2025
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

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Employ Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'Search' GET parameter in /search.php requests, focusing on abnormal input patterns or excessive request rates. 2) Implement rate limiting and request throttling on the search endpoint to reduce the risk of resource exhaustion. 3) Conduct code review and apply temporary input validation or sanitization on the search parameter if source code access is available, rejecting suspicious or malformed inputs. 4) Monitor application logs and network traffic for unusual spikes or patterns indicative of exploitation attempts. 5) Consider isolating or temporarily disabling the search functionality if it is not critical, until a patch or update is available. 6) Engage with the open-source community or maintainers to track any unofficial patches or forks addressing this issue. 7) Maintain up-to-date backups and incident response plans to quickly recover from potential service disruptions.

Description

A vulnerability classified as problematic was found in chaitak-gorai Blogbook up to 92f5cf90f8a7e6566b576fe0952e14e1c6736513. This vulnerability affects unknown code of the file /search.php of the component GET Parameter Handler. The manipulation of the argument Search leads to denial of service. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using chaitak-gorai Blogbook, this vulnerability could lead to denial of service conditions, rendering the affected web application or service unavailable. This can disrupt business operations, degrade user experience, and potentially cause reputational damage if public-facing services are impacted. While the vulnerability does not directly compromise data confidentiality or integrity, availability loss can affect critical communication or content delivery platforms relying on Blogbook. Organizations in sectors with high availability requirements, such as media, publishing, or public information portals, may face operational risks. Additionally, the lack of vendor response and patch availability increases the window of exposure, potentially inviting attackers to exploit the vulnerability once automated tools incorporate the public exploit details. The medium severity suggests moderate impact, but the ease of exploitation without authentication and user interaction increases the likelihood of opportunistic attacks.

Summary

CVE-2025-5404 is a medium severity vulnerability affecting the chaitak-gorai Blogbook software, specifically in the /search.php component that handles GET parameters. The vulnerability arises from improper handling of the 'Search' argument, which can be manipulated by an attacker to trigger a denial of service (DoS) condition. This DoS likely results from resource exhaustion or application crash caused by malformed or malicious input to the search functionality. The vendor was contacted but did not respond, leaving users without vendor-supported remediation. The CVSS 4.0 base score of 5.3 reflects a medium severity, with the vector indicating that the attack requires network access (AV:A), no privileges (PR:N), no user interaction (UI:N), and results in a loss of availability (VA:L) without impacting confidentiality or integrity. Public disclosure of the exploit exists, but no known active exploitation in the wild has been reported. The vulnerability is limited to the GET parameter handling in the search feature, which is a common entry point for web-based attacks. Given the lack of vendor response and patch, the risk remains until mitigations are applied by users or maintainers.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 9 Jul 2025, 12:57 UTC

Technical details

References

Community reviews

Related threats