What is the CVSS score of EUVD-2025-16578?

EUVD-2025-16578 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. EPSS exploitation probability: 0.1%.

Which versions of PHP are affected by EUVD-2025-16578?

A critical SQL injection vulnerability in the Blogbook application's administrative post editing functionality allows unauthenticated remote attackers to compromise the database and potentially…

Is there a public PoC exploit available for EUVD-2025-16578?

Yes, a public proof-of-concept exploit is available for EUVD-2025-16578. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate EUVD-2025-16578?

Within 24 hours: Identify and inventory all systems running Blogbook; disable public access to /admin/includes/edit_post.php if possible; enable enhanced logging and monitoring for SQL injection attempts. Within 7 days: Implement Web Application Firewall (WAF) rules to block SQL injection patterns in the edit_post_id parameter; conduct emergency security assessment of administrative interfaces. Within 30 days: Evaluate migration to alternative maintained solutions; if staying with Blogbook, establish continuous vulnerability scanning and prepare incident response procedures for potential exploitation.

PHP EUVD-2025-16578

| CVE-2025-5402 HIGH

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)

2025-06-01 cna@vuldb.com

PHP SQLi Blogbook Chaitak Gorai

7.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 16:42 euvd

EUVD-2025-16578

Analysis Generated

Mar 14, 2026 - 16:42 vuln.today

PoC Detected

Nov 10, 2025 - 20:11 vuln.today

Public exploit code

CVE Published

Jun 01, 2025 - 14:15 nvd

HIGH 7.3

DescriptionCVE.org

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.

AnalysisAI

Critical SQL injection vulnerability in chaitak-gorai Blogbook affecting the GET parameter handler in /admin/includes/edit_post.php, specifically the 'edit_post_id' parameter. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially leading to data exfiltration, modification, or denial of service. The vulnerability has been publicly disclosed with exploit code available, and the vendor has not responded to early disclosure notifications.

Technical ContextAI

This vulnerability exists in the Blogbook blogging platform's administrative interface, specifically in the edit post functionality. The root cause is classified as CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component - 'Injection'), which indicates insufficient input validation/sanitization of the 'edit_post_id' GET parameter before it is used in SQL queries. The affected component is the GET Parameter Handler in /admin/includes/edit_post.php, suggesting the parameter is parsed from query strings and directly concatenated or insufficiently escaped in database queries. The continuous delivery model with rolling releases means traditional version tracking is absent, making it difficult to establish precise affected version ranges beyond the identified commit hash (92f5cf90f8a7e6566b576fe0952e14e1c6736513).

RemediationAI

Immediate remediation steps: (1) Audit all instances of Blogbook for vulnerability presence by reviewing /admin/includes/edit_post.php for parameterized query usage on 'edit_post_id'; (2) Update to the latest repository commit beyond 92f5cf90f8a7e6566b576fe0952e14e1c6736513 if available; (3) If update is unavailable, implement immediate mitigations including: parameterized prepared statements for all SQL queries using 'edit_post_id', input validation to ensure the parameter is a valid integer, Web Application Firewall (WAF) rules to detect/block SQL injection patterns in GET parameters, and restrict admin panel access to trusted IP ranges pending patch deployment; (4) Monitor application logs for suspicious 'edit_post_id' parameter values (SQL keywords, quotes, comment syntax); (5) Consider forking and patching the code locally given vendor non-responsiveness; (6) Implement least-privilege database accounts to limit SQL injection impact scope.