CVE-2009-3418
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 Plume CMS 1.2.3 allow (1) remote authenticated users to execute arbitrary SQL commands via the m parameter to manager/index.php and (2) remote authenticated administrators to execute arbitrary SQL commands via the id parameter in an edit_link action to manager/tools.php. NOTE: some of these details are obtained 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 · high confidencePlume CMS 1.2.3 contains two SQL injection vulnerabilities: one allowing authenticated users to execute arbitrary SQL commands via the m parameter in manager/index.php, and another allowing authenticated administrators to execute arbitrary SQL via the id parameter in the edit_link action in manager/tools.php.
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.2.3CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/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.
-
Confirm Plume CMS is installedLook for the Plume CMS installation directory on the web server. Check for the presence of characteristic files such as index.php in the root, or the manager/ subdirectory. Common paths include /plume/, /cms/, or the web root.Affected if Plume CMS files are found on the server and the manager interface is accessible via web.
-
Identify the Plume CMS versionCheck the version file or header typically found in Plume CMS. Look for a version.php, VERSION file, or check the footer of the main index page for version information. Compare the installed version to the affected version 1.2.3.Affected if The installed version is exactly 1.2.3.
-
Verify manager/index.php existsLocate the file manager/index.php within the Plume CMS installation directory. Inspect the file for the presence of the 'm' parameter handling in the code.Affected if The file manager/index.php exists and processes the 'm' parameter without proper sanitization.
-
Verify manager/tools.php existsLocate the file manager/tools.php within the Plume CMS installation directory. Inspect the file for the 'edit_link' action handling and the 'id' parameter processing.Affected if The file manager/tools.php exists and contains the edit_link action that uses the 'id' parameter unsafely.
-
Confirm authentication is possibleDetermine if user authentication to the manager interface is configured and operational. Check if user accounts exist and the login form at manager/index.php is functional.Affected if Authenticated access to the manager interface is possible, which is required to exploit either SQL injection vulnerability.
The environment is affected if Plume CMS version 1.2.3 is installed, the manager interface is accessible, and unauthenticated or authenticated users can reach the vulnerable parameters in manager/index.php (m parameter) or manager/tools.php (id parameter in edit_link action).
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 a patched version of Plume CMS that addresses these SQL injection vulnerabilities, or refactor the affected code to use parameterized queries instead of string concatenation for SQL construction.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-3418 — 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-2009-3418 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