Atom ModulePlugin / extension · Drupal
CVE-2008-0275
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 · uneditedThe Atom 4.7 before 4.7.x-1.0 and 5.x before 5.x-1.0 module for Drupal does not properly manage permissions for node (1) titles, (2) teasers, and (3) bodies, which might allow remote attackers to gain access to syndicated content.
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 confidenceThe Drupal Atom module (versions 4.7 before 4.7.x-1.0 and 5.x before 5.x-1.0) fails to properly enforce access controls on node titles, teasers, and bodies when generating syndicated Atom/RSS feeds, potentially exposing restricted content to unauthorized users.
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
Atom ModulePlugin / extension
<= 4.7<= 5.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
- 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.
-
Verify Atom module is installedLocate the atom module directory in sites/all/modules or sites/default/modules, or check via Drupal admin interface at admin/build/modules. Also check the .info file within the atom module folder for name and version details.Affected if The Atom module directory exists in the Drupal modules folder and the .info file identifies it as the Atom module.
-
Determine installed Atom module versionOpen the atom.info file in the atom module directory and read the version line, or check the version displayed in Drupal's admin interface at admin/build/modules.Affected if Version is 4.7.x (any version before 4.7.x-1.0) or 5.x (any version before 5.x-1.0), which corresponds to versions <= 4.7 or <= 5.0 as listed in the affected products.
-
Confirm Atom/RSS feeds are enabledCheck Drupal's feed settings at admin/build RSS or look for feed URLs on the site (paths ending in /feed, /atom, or /rss.xml). Also check if any content types have syndication enabled in their settings.Affected if Atom or RSS feeds are actively being generated and accessible on the site.
-
Identify content accessible via feedsVisit the site's feed URLs and examine what content types (node titles, teasers, bodies) are included. Cross-reference with content types that have restricted access settings in Drupal's permissions or content access modules.Affected if The feeds display node content that should be restricted based on Drupal's user role permissions, indicating the access control bypass is occurring.
A user is affected if the Drupal Atom module is installed with version 4.7.x before 1.0 or 5.x before 1.0 AND Atom/RSS feeds are enabled, allowing unauthorized access to restricted node content.
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 the Drupal Atom module to version 4.7.x-1.0 or 5.x-1.0 or later to remediate the permission bypass. Audit existing feeds for unauthorized content exposure.
Fix this in Atom Module
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0275 — 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-2008-0275 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