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

> Authenticated users can bypass node restrictions to read, edit, or delete content due to improper access checks in the Keyboard Shortcut Utility module.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/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:** 19 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-px6m-q325-4c4f

## What is CVE-2013-0226?

CVE-2013-0226 is a medium-severity missing authorization vulnerability in n/a, published on 19 Mar 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Keyboard Shortcut Utility module 7.x-1.x before 7.x-1.1 for Drupal does not properly check node restrictions, which allows (1) remote authenticated users with the "view shortcuts" permission to read nodes or (2) remote authenticated users with the "admin shortcuts" permission to read, edit, or delete nodes via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Zugec Ivan Keyboard Shortcut Utility.

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

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

## Is CVE-2013-0226 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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