VulnerabilityPublished 1 Jun 2025

CVE-2025-5407: chaitak-gorai Blogbook · Cross-site Scripting

Affects chaitak-gorai BlogbookSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

4.8Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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

These include applying strict input validation and output encoding on the 'fullname' parameter at the application or web server level to neutralize malicious scripts. Employing a Web Application Firewall (WAF) with custom rules to detect and block suspicious payloads targeting /register_script.php can reduce risk. Organizations should also conduct thorough code reviews and security testing to identify and remediate similar injection points. User awareness campaigns to recognize phishing attempts can mitigate social engineering risks stemming from XSS exploitation. Monitoring web logs for unusual activity related to the vulnerable endpoint is advised. Finally, organizations should consider isolating or disabling the vulnerable functionality if feasible until a vendor fix is available.

Description

A vulnerability has been found in chaitak-gorai Blogbook up to 92f5cf90f8a7e6566b576fe0952e14e1c6736513 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /register_script.php. The manipulation of the argument fullname leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. It is recommended to upgrade the affected component. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using the chaitak-gorai Blogbook platform, this XSS vulnerability poses a risk primarily to the confidentiality and integrity of user sessions and data. Successful exploitation could lead to session hijacking, credential theft, or the injection of malicious content, potentially damaging user trust and organizational reputation. Given the remote exploitability and the lack of vendor response, organizations may face challenges in timely patching, increasing exposure. The impact is particularly significant for organizations handling sensitive user data or those with high web traffic, as attackers could leverage this vulnerability to conduct phishing campaigns or spread malware. Although the vulnerability does not directly affect availability, the indirect consequences such as reputational damage and potential regulatory scrutiny under GDPR for inadequate protection of user data could be substantial.

Summary

CVE-2025-5407 is a cross-site scripting (XSS) vulnerability identified in the chaitak-gorai Blogbook application, specifically affecting an unknown functionality within the /register_script.php file. The vulnerability arises from improper sanitization or validation of the 'fullname' parameter, which can be manipulated by an attacker to inject malicious scripts. This flaw allows remote attackers to execute arbitrary JavaScript code in the context of the victim's browser when they visit a crafted URL or interact with the vulnerable functionality. The vulnerability is classified as problematic and has a CVSS 4.8 (medium) score, indicating a moderate risk. The exploit does not require authentication but does require user interaction (e.g., the victim must visit a malicious link). The vendor has not responded to disclosure attempts, and no patches or versioning information are available, complicating remediation efforts. The product does not use versioning, making it difficult to determine unaffected versions. Although no known exploits are currently in the wild, the public disclosure of the exploit code increases the risk of exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

Technical details

References

Community reviews

Related threats