dbcve.org
BlogbookApplication · Chaitak Gorai

CVE-2025-5402

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-01
Fix available
A fix is available. Upgrade to after 2021-11-22 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in chaitak-gorai Blogbook up to 92f5cf90f8a7e6566b576fe0952e14e1c6736513. It has been rated as critical. Affected by this issue is some unknown functionality of the file /admin/includes/edit_post.php of the component GET Parameter Handler. The manipulation of the argument edit_post_id leads to sql injection. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Blogbook's /admin/includes/edit_post.php via the edit_post_id GET parameter. An unauthenticated remote attacker can manipulate SQL queries by injecting malicious input through this parameter, potentially allowing database exposure, data exfiltration, or unauthorized administrative actions.

MitigationImplement prepared statements/parameterized queries for all database operations involving the edit_post_id parameter in edit_post.php. Until a patched version is released, restrict administrative access via network-level controls or authentication middleware.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BlogbookApplication
Affected:<= 2021-11-22

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Blogbook installation
    Locate the Blogbook application files on your server - check web root directories for blogbook, blog, or similar application folders.
    Affected if The application is not installed on this system, so this CVE does not apply.
  2. Identify installed version
    Check for version files, readme files, or metadata within the Blogbook installation that indicates the version date. Compare against the affected date 2021-11-22.
    Affected if The installed version is dated 2021-11-22 or earlier.
  3. Locate vulnerable file
    Check for the existence of /admin/includes/edit_post.php within the Blogbook installation directory.
    Affected if The file /admin/includes/edit_post.php exists in the installation.
  4. Verify admin panel is accessible
    Attempt to access the admin panel URL endpoint /admin/ or confirm the admin route is enabled in the web server configuration.
    Affected if The admin panel is publicly or internally accessible.
  5. Inspect vulnerable parameter usage
    Examine the edit_post.php file source code and look for direct usage of the edit_post_id GET parameter in SQL queries without prepared statements or sanitization.
    Affected if The edit_post_id parameter is used directly in SQL queries without parameterization.

A user is affected if Blogbook version 2021-11-22 or earlier is installed, the vulnerable edit_post.php file exists, and the admin panel is accessible with the SQL injection present in the edit_post_id parameter handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2021-11-22
Interim mitigation

Implement prepared statements/parameterized queries for all database operations involving the edit_post_id parameter in edit_post.php. Until a patched version is released, restrict administrative access via network-level controls or authentication middleware.

Fix this in Blogbook Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5402 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data