# CVE-2013-4187: Information disclosure in Flippy

> Authenticated users can bypass access restrictions to view links or aliases for restricted nodes in the Drupal Flippy module.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2013-4224, GHSA-cc75-4632-rm7f

## What is CVE-2013-4187?

CVE-2013-4187 is a medium-severity vulnerability in Flippy, published on 30 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2013-4187?

It affects 1 product.


Products: Flippy Project Flippy.

## How do I fix CVE-2013-4187?

No fix has been published for CVE-2013-4187 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-4187 being exploited?

There is no known exploitation of CVE-2013-4187 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4187 and fix it if it is affected.

What it is: CVE-2013-4187 is a medium-severity vulnerability in Flippy, published on 30 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4187 in the wild and no public exploit code.

Affected product: Flippy. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4187/ (Markdown: https://insights.sbomify.com/CVE-2013-4187/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4187
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4187
- OSV: https://osv.dev/vulnerability/CVE-2013-4187

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4187/
Summaries are generated and may contain mistakes; the official description above is the record.