# CVE-2012-4483: Missing authorization in n/a

> Remote attackers can bypass node access restrictions to view sensitive recent comments in the Drupal Commons 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:** 31 Oct 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-gxjc-3gfg-2x5c

## What is CVE-2012-4483?

CVE-2012-4483 is a medium-severity missing authorization vulnerability in n/a, published on 31 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The commons_discussion_views_default_views function in modules/features/commons_discussion/commons_discussion.views_default.inc in the Drupal Commons module 6.x-2.x before 6.x-2.8 for Drupal does not properly enforce intended node access restrictions, which might allow remote attackers to obtain sensitive information via the recent comments listing.

Weakness: CWE-264

## Which versions are affected by CVE-2012-4483?

It affects 1 product.


Products: Acquia Commons.

## How do I fix CVE-2012-4483?

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

## Is CVE-2012-4483 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1907](https://insights.sbomify.com/CVE-2013-1907/): Missing authorization in n/a (medium 5.0)
- [CVE-2013-1908](https://insights.sbomify.com/CVE-2013-1908/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4483 and fix it if it is affected.

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

## Sources

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

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