dbcve.org
SimplogApplication

CVE-2005-3076

HIGH · 7.5 CVSS v2.0 Published 2005-09-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Simplog 0.9.1 might allow remote attackers to execute arbitrary SQL commands or trigger SQL error messages via invalid (1) pid, (2) blogid, (3) cid, or (4) m parameters to archive.php, or the (5) blogid parameter to blogadmin.php.

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

Simplog 0.9.1 contains SQL injection vulnerabilities in archive.php (via pid, blogid, cid, m parameters) and blogadmin.php (via blogid parameter). Attackers can inject arbitrary SQL commands or cause SQL error messages to be displayed, potentially allowing data exfiltration or database compromise.

MitigationUpgrade to a patched version of Simplog or implement strict input validation and parameterized queries (prepared statements) for all user-supplied parameters in archive.php and blogadmin.php to prevent SQL injection.

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
SimplogApplication
Affected:= 0.9.1

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
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 checks

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

  1. Locate Simplog installation directory
    Search the web server's document root for files named 'archive.php' or 'blogadmin.php', or look for a directory containing Simplog-specific files (such as config.php, functions.php, or a 'simplog' folder name).
    Affected if Simplog is installed and accessible on the server.
  2. Identify Simplog version
    Check for a version indicator in Simplog files. Look in config.php, version.php, or the main index.php for a version string like '0.9.1', or check the comment headers in archive.php or blogadmin.php for version information.
    Affected if The installed version is exactly 0.9.1.
  3. Verify vulnerable files exist
    Confirm that archive.php and blogadmin.php exist in the Simplog installation directory. These are the files containing the SQL injection vulnerabilities via the pid, blogid, cid, and m parameters in archive.php, and the blogid parameter in blogadmin.php.
    Affected if Both archive.php and blogadmin.php are present in the Simplog installation.
  4. Check parameter handling in archive.php
    Examine the source code of archive.php to verify that parameters pid, blogid, cid, and m are used in SQL queries without proper escaping, parameterization, or input validation. Look for direct insertion of $_GET or $_POST variables into SQL statements.
    Affected if The parameters pid, blogid, cid, or m are used in SQL queries without prepared statements or input sanitization.
  5. Check parameter handling in blogadmin.php
    Examine the source code of blogadmin.php to verify that the blogid parameter is used in SQL queries without proper escaping, parameterization, or input validation.
    Affected if The blogid parameter is used in SQL queries without prepared statements or input sanitization.

A user is affected if Simplog version 0.9.1 is installed and the vulnerable files archive.php or blogadmin.php contain unsanitized SQL queries using the specified parameters.

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

Upgrade to a patched version of Simplog or implement strict input validation and parameterized queries (prepared statements) for all user-supplied parameters in archive.php and blogadmin.php to prevent SQL injection.

Fix this in Simplog Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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