# CVE-2025-5407: chaitak-gorai Blogbook register_script.php cross site scripting

> Remote attackers can inject malicious scripts via the fullname parameter in the registration script of the Blogbook web application.

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jun 2025
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-p9pm-v555-5528

## What is CVE-2025-5407?

CVE-2025-5407 is a medium-severity cross-site scripting vulnerability in chaitak-gorai Blogbook, published on 1 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-5407?

It affects 1 product.


Products: Chaitak-Gorai Blogbook.

## How do I fix CVE-2025-5407?

No fix has been published for CVE-2025-5407 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-5407 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5407 exists.

## Other vulnerabilities in chaitak-gorai Blogbook

- [CVE-2025-5400](https://insights.sbomify.com/CVE-2025-5400/): chaitak-gorai Blogbook GET Parameter user.php sql injection (medium 6.9)
- [CVE-2025-5401](https://insights.sbomify.com/CVE-2025-5401/): chaitak-gorai Blogbook GET Parameter post.php sql injection (medium 6.9)
- [CVE-2025-5402](https://insights.sbomify.com/CVE-2025-5402/): chaitak-gorai Blogbook GET Parameter edit_post.php sql injection (medium 6.9)
- [CVE-2025-5403](https://insights.sbomify.com/CVE-2025-5403/): chaitak-gorai Blogbook GET Parameter view_all_posts.php sql injection (medium 5.3)
- [CVE-2025-5404](https://insights.sbomify.com/CVE-2025-5404/): chaitak-gorai Blogbook GET Parameter search.php denial of service (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5407 and fix it if it is affected.

What it is: CVE-2025-5407 is a medium-severity cross-site scripting vulnerability in chaitak-gorai Blogbook, published on 1 Jun 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5407 exists.

Affected product: chaitak-gorai Blogbook. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-5407/ (Markdown: https://insights.sbomify.com/CVE-2025-5407/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-5407
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-5407
- OSV: https://osv.dev/vulnerability/CVE-2025-5407

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-5407/
Summaries are generated and may contain mistakes; the official description above is the record.