FlippyDrupal extension · Flippy Project
CVE-2013-4187
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 Flippy module 7.x-1.x before 7.x-1.2 for Drupal does not properly restrict access to nodes, which allows remote authenticated users with the permission to access content to read a link or alias to a restricted node.
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 confidenceThe Flippy module 7.x-1.x before 7.x-1.2 for Drupal fails to enforce proper node access controls when rendering navigation links between nodes. Authenticated users with the basic 'access content' permission can view links or aliases to restricted nodes they should not have access to, resulting in information disclosure of node existence and paths.
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
FlippyDrupal extension
>= 7.x-1.0, <= 7.x-1.2= 7.x-1.xCVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify Flippy module installation and versionQuery the Drupal database: SELECT name, info FROM system WHERE name = 'flippy' AND type = 'module'; or check sites/all/modules/flippy/flippy.info for version line.Affected if The installed version is 7.x-1.0, 7.x-1.1, or 7.x-1.x before 7.x-1.2.
-
Verify Flippy is enabled on content typesCheck the Flippy module settings at admin/config/content/flippy or query the variable table for flippy_node_types to see which content types have Flippy navigation enabled.Affected if Flippy is enabled on any content type that has restricted (private) content.
-
Confirm presence of restricted nodesReview node access grants: SELECT nid, title FROM node WHERE status = 1; then check access rules in node_access table or review content types for access control modules (like node_access_user or organic groups) that restrict visibility.Affected if There exist nodes with access restrictions (private content, limited view permissions) on content types where Flippy is active.
-
Test for information disclosureAs an authenticated user with only basic 'access content' permission, navigate to nodes with Flippy arrows. Check if previous/next links appear for nodes the user should not have access to, or if node titles/paths for restricted content are visible in the navigation.Affected if Links or aliases to restricted nodes are visible to users who should not see them.
A user is affected if they have Flippy module version 7.x-1.0 through 7.x-1.2 installed, it is enabled on content types with restricted nodes, and users with basic access can see navigation links to restricted 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 dataUpdate Flippy module to version 7.x-1.2 or later which implements proper node access checks before displaying navigation links to restricted content.
Fix this in Flippy
Scoped from the published advisory
- Consultation2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4187 — 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-2013-4187 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