dbcve.org
Blog SiteApplication · Fabian

CVE-2025-13575

HIGH · 8.8 CVSS v3.1 Published 2025-11-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 security vulnerability has been detected in code-projects Blog Site 1.0. Impacted is the function category_exists of the file /resources/functions/blog.php of the component Category Handler. Such manipulation of the argument name/field leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. Multiple endpoints are affected.

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 · moderate confidence

SQL injection vulnerability in the category_exists function within /resources/functions/blog.php of code-projects Blog Site 1.0. The name parameter passed to this function is not properly sanitized, allowing attackers to inject malicious SQL queries. Multiple endpoints are affected by this issue.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements in the category_exists function and all affected endpoints. Validate and sanitize all user inputs before using them in SQL queries.

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
Blog SiteApplication
Affected:= 1.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Fabian Blog Site installation
    Check your web server for the presence of the Fabian Blog Site application, typically in the web root directory. Look for files like index.php or a folder named 'blog' that matches the expected structure of version 1.0.
    Affected if The Fabian Blog Site version 1.0 is installed on the server.
  2. Locate vulnerable file
    Verify the existence of /resources/functions/blog.php within the blog site installation directory. This file should contain the category_exists function.
    Affected if The file /resources/functions/blog.php exists and is part of the installed application.
  3. Inspect category_exists function
    Open /resources/functions/blog.php and locate the category_exists function. Examine how the 'name' parameter is handled - look for direct use of this parameter in SQL queries without sanitization functions like mysqli_real_escape_string, prepared statements, or parameter binding.
    Affected if The category_exists function contains SQL queries that use the 'name' parameter directly without proper sanitization or parameterized queries.
  4. Identify affected endpoints
    Search the application source code for all call sites where category_exists is invoked, particularly from files handling user requests such as admin panels, category creation forms, or API endpoints. Common locations include /admin/, /category/, or root-level PHP files.
    Affected if Any endpoint accepts user input (typically via GET or POST requests) and passes it to the category_exists function without validation.
  5. Test for input validation
    Review the application's input handling. Check if there is any input validation, sanitization, or web application firewall in place between user requests and the category_exists function call.
    Affected if There is no input validation or sanitization applied to the 'name' parameter before it reaches the vulnerable SQL query.
  6. Check for exploitation indicators
    Review web server access logs and application error logs for unusual SQL syntax patterns in requests related to category functionality, such as single quotes, UNION SELECT, or SQL keywords in parameter values.
    Affected if Logs show suspicious SQL injection patterns in parameters that would be passed to category_exists.

You are affected if Fabian Blog Site 1.0 is installed and the category_exists function in /resources/functions/blog.php processes user-supplied 'name' parameter without sanitization or parameterized queries.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements in the category_exists function and all affected endpoints. Validate and sanitize all user inputs before using them in SQL queries.

Fix this in Blog Site Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13575 — 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-13575 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