CVE-2006-2128
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 · uneditedMultiple SQL injection vulnerabilities in Pro Publish 2.0 allow remote attackers to execute arbitrary SQL commands via the (1) email and (2) password parameter to (a) admin/login.php, (3) find_str parameter to (b) search.php, or (4) artid parameter to (c) art.php, or (5) catid parameter to (d) cat.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 confidencePro Publish 2.0 contains multiple SQL injection vulnerabilities in four different PHP files (admin/login.php, search.php, art.php, and cat.php) where user-supplied input in parameters like email, password, find_str, artid, and catid is not properly sanitized before being used in database queries, allowing remote attackers to inject arbitrary SQL commands.
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= 2.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.
-
Locate Pro Publish installationSearch the web server document root for directories containing 'pro_publish', 'deltascripts', or the four vulnerable PHP files: admin/login.php, search.php, art.php, and cat.phpAffected if The application files are found on the server
-
Confirm version 2.0Check any version file (version.php, about.php, or meta tags in index.php) or look for version indicators in the application header/footer for the exact version numberAffected if The installed version is exactly 2.0
-
Verify vulnerable scripts existConfirm the presence of admin/login.php, search.php, art.php, and cat.php in the web-accessible Pro Publish directoryAffected if Any of the four vulnerable PHP files exist on the system
-
Check for unpatched SQL handling in admin/login.phpInspect the source code of admin/login.php for direct use of $_POST['email'] or $_POST['password'] in SQL queries without sanitization functions like mysql_real_escape_string or prepared statementsAffected if The email or password parameters are used in SQL queries without proper escaping or parameterized queries
-
Check for unpatched SQL handling in search.php, art.php, cat.phpInspect search.php for $_GET['find_str'], art.php for $_GET['artid'], and cat.php for $_GET['catid'] being used directly in SQL queries without sanitizationAffected if Any of these parameters (find_str, artid, catid) are used in SQL queries without proper escaping or parameterized queries
The system is affected if Deltascripts Pro Publish version 2.0 is installed and the vulnerable files (admin/login.php, search.php, art.php, cat.php) exist with unpatched SQL query handling of the identified parameters.
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 dataRemediate by implementing parameterized queries (prepared statements) for all database interactions in the affected files, and apply input validation/sanitization for all user-supplied parameters before they are used in SQL queries.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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 $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-2128 — 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-2006-2128 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