CVE-2010-0710
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 default.asp in ASPCode CMS 1.5.8, 2.0.0 Build 103, and possibly other versions, allows remote attackers to execute arbitrary SQL commands via the newsid parameter when the sec parameter is 26. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 · moderate confidenceSQL injection vulnerability in ASPCode CMS default.asp allows remote attackers to execute arbitrary SQL commands via the newsid parameter when the sec parameter is set to 26. This is a classic SQL injection flaw where user-supplied input (newsid) is not properly sanitized or parameterized before being used in SQL 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= 1.5.8= 2.0.0CVSS 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 if ASPCode CMS is installedSearch the web root for the file default.asp, which is the main entry point for this CMS. Check for the presence of directories or files containing 'aspcode' or 'aspcodecms' in the file system.Affected if The file default.asp exists in the web directory and appears to be ASPCode CMS.
-
Determine the installed version of ASPCode CMSOpen default.asp and look for version indicators such as a version variable, comment, or footer text. Alternatively, check for a changelog, readme, or version file in the CMS directory.Affected if The version is 1.5.8 or 2.0.0 exactly.
-
Verify the vulnerable parameter is accessibleSend a GET request to default.asp with sec=26 and observe if the page processes the newsid parameter. Example: /default.asp?sec=26&newsid=testAffected if The page returns without error and processes the newsid parameter, indicating the vulnerable code path is active.
-
Confirm SQL injection vulnerability existsInject a simple SQL payload into the newsid parameter such as newsid=1' (single quote). If the application returns a SQL error or behaves differently than newsid=1, the parameter is vulnerable.Affected if The application returns a database error or unexpected behavior when special SQL characters are passed to newsid.
The system is affected if ASPCode CMS version 1.5.8 or 2.0.0 is installed and the vulnerable default.asp page with sec=26 parameter is accessible and processes user input without sanitization.
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 parameterized queries or prepared statements for the newsid parameter in default.asp, and add proper input validation to prevent SQL injection attacks. Consider applying any available vendor patches for ASPCode CMS.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.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-2010-0710 — 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-2010-0710 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