CVE-2009-0929
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 · uneditedDirectory traversal vulnerability in the media manager in Nucleus CMS before 3.40 allows remote attackers to read arbitrary files via unknown vectors.
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 confidenceDirectory traversal vulnerability in the media manager of Nucleus CMS before version 3.40 allows remote attackers to read arbitrary files on the server through manipulation of path inputs, likely via '../' sequences to escape the intended directory bounds.
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<= 3.40= 3.0= 3.0_1= 3.0_rc= 3.1= 3.01= 3.2= 3.21= 3.22= 3.23CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Confirm Nucleus CMS installationSearch for Nucleus CMS files in the web root directory, typically in folders named 'nucleus' or check for the presence of index.php with Nucleus CMS brandingAffected if Nucleus CMS files are found on the server
-
Determine installed Nucleus CMS versionCheck the version file or the Nucleus administration panel. The version is often displayed on the login page footer or in a VERSION file in the installation directoryAffected if The installed version is 3.40 or lower, or the version cannot be determined (assumed vulnerable)
-
Verify media manager functionality is accessibleCheck if the media manager plugin is installed and accessible. Typically located at nucleus/plugins/manager/ or accessed via the admin panel under 'Media Files' sectionAffected if The media manager interface is accessible without additional authentication barriers beyond standard admin login
-
Test for directory traversal vulnerabilityIf you have access, attempt a controlled test using the media manager path parameter with a pattern such as '../../../' to escape the media directory. Check if the application allows path traversal sequences in filename or path parametersAffected if The application accepts '../' sequences in path or file parameters without rejecting or sanitizing them
A server is affected if Nucleus CMS version 3.40 or lower is installed and the media manager feature is accessible, as the directory traversal flaw allows reading files outside the intended media directory.
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 Nucleus CMS version 3.40 or later which contains the patch. If immediate upgrade is not possible, restrict web server access to the media manager directory and implement input validation for path parameters.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0929 — 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-0929 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