CVE-2025-5400VulnerabilityPublished 1 Jun 2025

CVE-2025-5400: chaitak-gorai Blogbook · SQL Injection

Affects chaitak-gorai BlogbookSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 08:11 UTC

CVSS 4.0 base score

6.9Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
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: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: 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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system 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 to 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 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

European organizations should immediately implement input validation and sanitization controls at the web application firewall (WAF) or reverse proxy level to filter and block malicious payloads targeting the 'u_id' parameter. Employing parameterized queries or prepared statements in any custom integrations with Blogbook can reduce injection risks. Network segmentation and strict access controls should be enforced to limit exposure of the Blogbook application to only trusted internal networks or VPN users. Continuous monitoring of logs for suspicious SQL query patterns related to 'u_id' parameters is essential to detect exploitation attempts early. Organizations should consider deploying runtime application self-protection (RASP) solutions to detect and block injection attacks in real time. Given the lack of vendor patches, organizations might explore temporary mitigation by disabling or restricting access to the vulnerable /user.php endpoint if feasible. Finally, organizations should prepare incident response plans specific to SQL injection attacks and ensure backups are current and tested for recovery.

Description

A vulnerability was found in chaitak-gorai Blogbook up to 92f5cf90f8a7e6566b576fe0952e14e1c6736513. It has been classified as critical. Affected is an unknown function of the file /user.php of the component GET Parameter Handler. The manipulation of the argument u_id leads to sql injection. It is possible to launch the attack remotely. 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 Blogbook, this vulnerability poses significant risks including unauthorized access to sensitive user data, potential data breaches, and disruption of service integrity. Exploitation could lead to exposure of personal data protected under GDPR, resulting in regulatory penalties and reputational damage. The ability to execute arbitrary SQL commands remotely without authentication increases the threat level, especially for organizations relying on Blogbook for user management or content delivery. The rolling release nature of the product and lack of vendor response complicate timely remediation, potentially leaving European entities exposed for extended periods. Attackers could leverage this vulnerability to pivot within networks, escalate privileges, or disrupt operations, impacting confidentiality, integrity, and availability of critical systems.

Summary

CVE-2025-5400 is a critical SQL Injection vulnerability identified in the chaitak-gorai Blogbook software, specifically affecting the /user.php file's GET parameter handler. The vulnerability arises from improper sanitization of the 'u_id' argument, allowing an attacker to inject malicious SQL code remotely without any authentication or user interaction. This flaw enables an attacker to manipulate backend database queries, potentially leading to unauthorized data access, data modification, or even complete compromise of the database. The product uses a rolling release model, which complicates version tracking and patch management, and the vendor has not responded to disclosure attempts. Although the CVSS 4.0 score is 6.9 (medium severity), the nature of SQL injection vulnerabilities typically warrants heightened concern due to their potential impact. The vulnerability does not require privileges or user interaction, making exploitation easier. No known exploits are currently reported in the wild, but public disclosure increases the risk of exploitation attempts. The absence of patches or updates necessitates immediate mitigation efforts by users of Blogbook to prevent exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 9 Jul 2025, 00:58 UTC

Technical details

References

Community reviews

Related threats