dbcve.org
Shop ScriptApplication · Webasyst Llc

CVE-2010-1463

HIGH · 7.5 CVSS v2.0 Published 2010-04-16
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 WebAsyst Shop-Script FREE allow attackers to execute arbitrary SQL commands via the (1) add2cart, (2) c_id, (3) categoryID, (4) list_price, (5) name, (6) new_offer, (7) price, (8) product_code, (9) productID, (10) rating, and (11) save_product parameters.

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

Multiple SQL injection vulnerabilities in WebAsyst Shop-Script FREE allow attackers to execute arbitrary SQL commands via 11 different parameters (add2cart, c_id, categoryID, list_price, name, new_offer, price, product_code, productID, rating, save_product). These parameters are not properly sanitized before being used in SQL queries, enabling attackers to inject malicious SQL code.

MitigationImplement parameterized queries (prepared statements) for all database operations using these parameters, combined with strict input validation and proper escaping as defense-in-depth.

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
Shop ScriptApplication
Affected:all versions

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 WebAsyst Shop-Script installation
    Search for Shop-Script files on the server, typically in the web root directory. Look for directories named 'shop-script', 'wa-system', or files containing 'shop-script' in the filename. Check for the presence of index.php or main.php that references 'shop-script' or 'WebAsyst'.
    Affected if The product WebAsyst Shop-Script is present on the server.
  2. Identify Shop-Script version
    Examine version files, typically in configuration files or the main index file. Check for version strings in files like version.php, about.php, or the installer. Common paths include /shop-script/ or the root web directory.
    Affected if Any version of WebAsyst Shop-Script is installed - all versions are affected per the CVE.
  3. Locate vulnerable parameter handlers
    Search the source code for the affected parameters: add2cart, c_id, categoryID, list_price, name, new_offer, price, product_code, productID, rating, save_product. Look in PHP files within the shop-script directory for code that handles these POST/GET parameters directly in SQL queries.
    Affected if The application code processes any of these 11 parameters without using prepared statements or proper sanitization.
  4. Check database query implementation
    Examine PHP files that construct SQL queries using these parameters. Look for patterns like 'SELECT ... WHERE productID = ' . $_REQUEST['productID'] or similar direct concatenation. Use grep to search for these parameters adjacent to SQL keywords like SELECT, INSERT, UPDATE, DELETE.
    Affected if SQL queries concatenate these parameters directly without parameterized queries or input sanitization.
  5. Test parameter processing
    Submit a harmless test value via one of the affected parameters (add2cart, productID, categoryID, etc.) and observe the application's response. Check if the input is reflected in SQL queries by enabling query logging or monitoring for errors.
    Affected if The application accepts and processes these parameters without validation, making them exploitable.

The environment is affected if WebAsyst Shop-Script is installed and the application processes user input through any of the 11 vulnerable parameters without proper SQL sanitization or prepared statements.

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

Implement parameterized queries (prepared statements) for all database operations using these parameters, combined with strict input validation and proper escaping as defense-in-depth.

Fix this in Shop Script Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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