# CVE-2012-6563: Information disclosure in n/a

> Remote attackers can read private entities in Elgg due to improper clearing of cached access lists during plugin boot.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/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:** 23 May 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qq49-hmp5-gwv6

## What is CVE-2012-6563?

CVE-2012-6563 is a medium-severity vulnerability in n/a, published on 23 May 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

engine/lib/access.php in Elgg before 1.8.5 does not properly clear cached access lists during plugin boot, which allows remote attackers to read private entities via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Elgg Elgg.

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

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

## Is CVE-2012-6563 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2936](https://insights.sbomify.com/CVE-2011-2936/): SQL injection in Elgg (critical 9.8)
- [CVE-2021-4072](https://insights.sbomify.com/CVE-2021-4072/): Cross-site Scripting (XSS) - Stored in elgg/elgg (critical 9.0)
- [CVE-2012-6562](https://insights.sbomify.com/CVE-2012-6562/): Missing authorization in n/a (medium 6.8)
- [CVE-2011-2935](https://insights.sbomify.com/CVE-2011-2935/): Elgg Reflected XSS Vulnerability (medium 6.1)
- [CVE-2019-11016](https://insights.sbomify.com/CVE-2019-11016/): Elgg open redirect (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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