CVE-2004-1570
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 · uneditedSQL injection vulnerability in bBlog 0.7.2 and 0.7.3 allows remote attackers to execute arbitrary SQL commands via the p parameter.
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 confidenceSQL injection vulnerability in bBlog 0.7.2 and 0.7.3 allows remote attackers to execute arbitrary SQL commands through the 'p' parameter without proper input sanitization or parameterized 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= 0.7.2= 0.7.3CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify bBlog installation versionLocate the bBlog installation and check the version file or metadata (commonly version.php, README, or admin interface footer) to confirm if the installed version is 0.7.2 or 0.7.3Affected if Installed version is 0.7.2 or 0.7.3 exactly (older versions like 0.7.1 or newer patched versions are not affected by this specific CVE)
-
Locate the vulnerable 'p' parameter handlerSearch the bBlog source code for files that handle the 'p' request parameter, typically in index.php or entry.php, and examine how this parameter is processedAffected if The 'p' parameter is used in SQL queries without sanitization or parameterized queries
-
Verify lack of input sanitization on the 'p' parameterInspect the code handling the 'p' parameter to confirm there is no mysql_real_escape_string, addslashes, or other input validation applied before using it in database queriesAffected if The code directly incorporates the 'p' parameter value into SQL queries without escaping or using prepared statements
-
Check if bBlog is accessible over the networkConfirm the bBlog web application is publicly or internally accessible and that the vulnerable parameter can be submitted via HTTP GET or POST requestsAffected if The application is live and the 'p' parameter can be reached via web requests
If bBlog version 0.7.2 or 0.7.3 is installed and the 'p' parameter is processed in SQL queries without sanitization or parameterized queries, the environment is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation on all parameters and refactor database queries to use parameterized queries or prepared statements to prevent SQL injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-1570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2004-1570 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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