# CVE-2013-2247: Missing authorization in n/a

> Remote attackers with low privileges can bypass access restrictions to view the permissions edit form in the Fast Permissions Administration module.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 28 Aug 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-57x4-jjg7-5m42

## What is CVE-2013-2247?

CVE-2013-2247 is a high-severity missing authorization vulnerability in n/a, published on 28 Aug 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Fast Permissions Administration module 6.x-2.x before 6.x-2.5 and 7.x-2.x before 7.x-2.3 for Drupal does not properly restrict access to the modal content callback, which allows remote attackers to obtain unspecified access to the permissions edit form.

Weakness: CWE-264

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

It affects 1 product.


Products: Fast Permissions Administration Project Fast Permission Administration.

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

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

## Is CVE-2013-2247 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2247 is a high-severity missing authorization vulnerability in n/a, published on 28 Aug 2013. 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-2247 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-2013-2247/ (Markdown: https://insights.sbomify.com/CVE-2013-2247/index.md)
```

## Sources

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

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