# CVE-2015-4389: Missing authorization in n/a

> Authenticated users can bypass content type creation restrictions in the Drupal Open Graph Importer module to create unauthorized content.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/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:** 15 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wfw2-cqm6-5xwc

## What is CVE-2015-4389?

CVE-2015-4389 is a medium-severity missing authorization vulnerability in n/a, published on 15 Jun 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Open Graph Importer (og_tag_importer) 7.x-1.x for Drupal does not properly check the create permission for content types created during import, which allows remote authenticated users to bypass intended restrictions by leveraging the "import og_tag_importer" permission.

Weakness: CWE-264

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

It affects 1 product.


Products: Open Graph Importer Project Open Graph Importer.

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

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

## Is CVE-2015-4389 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-4389 is a medium-severity missing authorization vulnerability in n/a, published on 15 Jun 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-4389 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-4389/ (Markdown: https://insights.sbomify.com/CVE-2015-4389/index.md)
```

## Sources

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

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