dbcve.org
A FaqApplication · Alan Ward

CVE-2005-4064

HIGH · 7.5 CVSS v2.0 Published 2005-12-07
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
Multiple SQL injection vulnerabilities in A-FAQ 1.0 allow remote attackers to execute arbitrary SQL commands via the (1) faqid parameter to faqDspItem.asp and (2) catcode parameter to faqDsp.asp.

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

A-FAQ 1.0 contains SQL injection vulnerabilities in two ASP pages: faqDspItem.asp (faqid parameter) and faqDsp.asp (catcode parameter). User-supplied input is not properly sanitized before being used in SQL queries, allowing remote attackers to inject arbitrary SQL commands.

MitigationReplace dynamic SQL queries with parameterized queries or prepared statements in both affected ASP files, and implement proper input validation for the faqid and catcode parameters.

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
A FaqApplication
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
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 A-FAQ installation files
    Search the web server filesystem for the presence of faqDspItem.asp and faqDsp.asp files, typically found in the web root or an /faq/ subdirectory.
    Affected if Both faqDspItem.asp and faqDsp.asp files exist in the web directory, indicating A-FAQ is installed.
  2. Verify A-FAQ version
    Inspect the file headers, any included version files, or the main index page to confirm the installed version is 1.0.
    Affected if The installed version is Alan Ward A Faq 1.0.
  3. Confirm vulnerable parameters are exposed
    Test if the faqid parameter on faqDspItem.asp and the catcode parameter on faqDsp.asp are accessible via HTTP GET requests by requesting URLs such as /faqDspItem.asp?faqid=1 and /faqDsp.asp?catcode=1.
    Affected if Both parameters are accessible and the pages return expected output without authentication barriers.
  4. Check for input sanitization in faqDspItem.asp
    Open faqDspItem.asp in a text editor and locate the code handling the faqid parameter. Search for SQL query construction patterns and verify whether the faqid value is used directly in a query string or passed to a database without sanitization functions (e.g., Replace, Server.HTMLEncode, or parameterized queries).
    Affected if The faqid parameter is concatenated directly into a SQL query without parameterized binding or input validation routines.
  5. Check for input sanitization in faqDsp.asp
    Open faqDsp.asp in a text editor and locate the code handling the catcode parameter. Examine whether the catcode value is used in SQL query construction without sanitization or parameterized queries.
    Affected if The catcode parameter is concatenated directly into a SQL query without parameterized binding or input validation routines.

The environment is affected if Alan Ward A Faq version 1.0 is installed with accessible faqDspItem.asp and faqDsp.asp files where the faqid and catcode parameters are used directly in SQL queries 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 or prepared statements in both affected ASP files, and implement proper input validation for the faqid and catcode parameters.

Fix this in A Faq Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

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