CVE-2012-2937
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 Pligg CMS before 1.2.2 allow remote attackers to execute arbitrary SQL commands via the (1) list parameter in a move action to admin/admin_index.php, (2) display parameter in a minimize action to admin/admin_index.php, (3) enabled[] parameter to admin/admin_users.php, or (4) msg_id to the module.php in the simple_messaging module.
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 confidenceMultiple SQL injection vulnerabilities in Pligg CMS before version 1.2.2 allow remote attackers to execute arbitrary SQL commands via four attack vectors: the list parameter in admin/admin_index.php move action, the display parameter in admin/admin_index.php minimize action, the enabled[] parameter in admin/admin_users.php, and the msg_id parameter in module.php for the simple_messaging module.
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 dataall versions<= 1.2.1= 1.0.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.1.0= 1.1.2= 1.1.3= 1.1.4= 1.1.5CVSS 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 Pligg CMS versionCheck the version file in your Pligg installation (commonly version.php or similar file in the root directory) or look at the admin dashboard for version informationAffected if Version is 1.2.1 or earlier, or any version listed as affected (1.0.0 through 1.1.5, or any version <=1.2.1)
-
Verify admin interface accessibilityConfirm whether the /admin/ directory is accessible from the network. This is required for the admin_index.php attack vectors to be exploitableAffected if Admin interface is exposed to untrusted users (not restricted by network ACLs, VPN, or strong authentication)
-
Check simple_messaging module statusLook for the simple_messaging module in your Pligg modules directory or check the module configuration in the admin panel to see if it is enabledAffected if The simple_messaging module is installed and enabled, exposing the module.php msg_id vulnerability
-
Inspect vulnerable parameter usageReview HTTP request logs or web application firewall logs for suspicious requests to admin/admin_index.php with the 'list' or 'display' parameters, to admin/admin_users.php with 'enabled[]' parameter, or to module.php with 'msg_id' parameterAffected if Any recent HTTP requests containing these parameters show signs of SQL injection attempts (unusual characters, database syntax in parameter values)
You are affected if your Pligg CMS version is 1.2.1 or earlier AND either the admin interface is network-accessible or the simple_messaging module is enabled.
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 dataUpgrade to Pligg CMS 1.2.2 or later to obtain patched code with proper input sanitization for SQL injection prevention.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2937 — 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-2012-2937 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