dbcve.org
Metacart2Application · Metalinks

CVE-2005-1363

HIGH · 7.5 CVSS v2.0 Published 2005-05-02
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 MetaCart 2.0 for PayFlow allow remote attackers to execute arbitrary commands via (1) intCatalogID, (2) strSubCatalogID, or (3) strSubCatalog_NAME parameter to productsByCategory.asp, (4) curCatalogID, (5) strSubCatalog_NAME, (6) intCatalogID, or (7) page parameter to productsByCategory.asp or (8) intProdID parameter to product.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

SQL injection vulnerabilities in MetaCart 2.0 allow remote attackers to execute arbitrary SQL commands via multiple parameters (intCatalogID, strSubCatalogID, strSubCatalog_NAME, curCatalogID, page, intProdID) in productsByCategory.asp and product.asp pages. User-supplied input is directly concatenated into SQL queries without proper sanitization or parameterized queries.

MitigationReplace direct string concatenation with parameterized queries/prepared statements for all identified vulnerable parameters. Implement strict input validation and employ least-privilege database accounts to limit the impact of any successful 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
Metacart2Application
Affected:= payflow_link

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. Confirm MetaCart 2.0 installation
    Locate the MetaCart installation directory on the web server. Check for the presence of the payflow_link component or any files named productsByCategory.asp and product.asp.
    Affected if MetaCart 2.0 is installed with the vulnerable ASP pages present.
  2. Identify vulnerable pages
    Locate the files productsByCategory.asp and product.asp within the web application directory structure.
    Affected if Both files exist in the web root or application folder.
  3. Examine SQL query construction in productsByCategory.asp
    Open productsByCategory.asp in a text editor and search for SQL query strings. Look for occurrences of the parameters intCatalogID, strSubCatalogID, strSubCatalog_NAME, curCatalogID, and page being concatenated directly into SQL statements using & or + operators without using parameterized queries or prepared statements.
    Affected if Any of these parameters are concatenated directly into SQL queries without sanitization or parameter binding.
  4. Examine SQL query construction in product.asp
    Open product.asp and review the code for SQL query construction. Look for the parameter intProdID being used in SQL queries without parameterized queries or input validation.
    Affected if The intProdID parameter is concatenated directly into SQL queries without sanitization or parameter binding.
  5. Verify database account privileges
    Check the database connection configuration used by the application. Identify the database user credentials configured in the connection string or configuration files.
    Affected if The database account has elevated privileges (such as db_owner or sysadmin roles) rather than limited read/write permissions for specific tables only.

A user is affected if MetaCart 2.0 is installed with productsByCategory.asp or product.asp present and any vulnerable parameters are used in SQL queries through direct concatenation without 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 direct string concatenation with parameterized queries/prepared statements for all identified vulnerable parameters. Implement strict input validation and employ least-privilege database accounts to limit the impact of any successful injection.

Fix this in Metacart2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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