CVE-2007-3128
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 content.php in WSPortal 1.0, when magic_quotes_gpc is disabled, allows remote attackers to execute arbitrary SQL commands via the page parameter.
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 confidenceSQL injection vulnerability in WSPortal 1.0's content.php allows remote attackers to inject arbitrary SQL commands via the page parameter when magic_quotes_gpc is disabled, enabling data exfiltration or manipulation.
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.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
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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 WSPortal installationLocate the WSPortal application files on the server, typically in the web root directory. Look for the content.php file in the application structure.Affected if WSPortal 1.0 is installed and content.php is present
-
Verify installed versionCheck the application version by examining any version files, README, or the main index page that displays the software version.Affected if Installed version is WSPortal 1.0
-
Check magic_quotes_gpc settingCreate a PHP info file (<?php phpinfo(); ?>) or check the PHP configuration file (php.ini) for the magic_quotes_gpc directive.Affected if magic_quotes_gpc is set to Off or 0
-
Inspect content.php for dynamic SQLExamine the content.php file source code to identify if the 'page' parameter is used in dynamic SQL query construction without proper escaping or parameterized queries.Affected if The page parameter is directly incorporated into SQL queries without sanitization
-
Confirm parameter exposureTest if the 'page' parameter in content.php accepts user input via GET or POST request (e.g., content.php?page=test).Affected if The page parameter processes user-supplied input without validation
A user is affected if WSPortal 1.0 is installed, content.php handles the page parameter, and magic_quotes_gpc is disabled, allowing SQL injection via unsanitized parameter input.
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 dataReplace dynamic SQL query construction with parameterized queries/prepared statements, and ensure magic_quotes_gpc is enabled or implement proper input sanitization/escaping as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3128 — 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-2007-3128 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