# CVE-2015-3391: Information disclosure in n/a

> Remote attackers can bypass access restrictions to view sensitive node titles via 403 pages in the Drupal Path Breadcrumbs module.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6r7-7j52-94w6

## What is CVE-2015-3391?

CVE-2015-3391 is a medium-severity vulnerability in n/a, published on 21 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Path Breadcrumbs module before 7.x-3.2 for Drupal allows remote attackers to bypass intended access restrictions and obtain sensitive node titles by reading a 403 Not Found page.

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

## Which versions are affected by CVE-2015-3391?

It affects 1 product.


Products: Path Breadcrumbs Project Path Breadcrumbs.

## How do I fix CVE-2015-3391?

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

## Is CVE-2015-3391 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6754](https://insights.sbomify.com/CVE-2015-6754/): Cross-site scripting in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-3391 and fix it if it is affected.

What it is: CVE-2015-3391 is a medium-severity vulnerability in n/a, published on 21 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3391 in the wild and no public exploit code.

Affected product: n/a. 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-2015-3391/ (Markdown: https://insights.sbomify.com/CVE-2015-3391/index.md)
```

## Sources

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

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