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

> An insecure direct object reference in ez Publish allows attackers to access or modify unauthorized data.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 6 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wcmp-f6cg-hwcq

## What is CVE-2012-1565?

CVE-2012-1565 is a high-severity missing authorization vulnerability in n/a, published on 6 Oct 2012. It can be exploited over the network.

### Official description

Unspecified vulnerability in ez Publish 4.1.4, 4.2, 4.3, 4.4, 4.5, and 4.6 has unknown impact and attack vectors related to an insecure direct object reference.

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

It affects 1 product.


Products: Ez Ez Publish.

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

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

## Is CVE-2012-1565 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-4493](https://insights.sbomify.com/CVE-2007-4493/): Missing authorization in n/a (critical 10.0)
- [CVE-2005-4853](https://insights.sbomify.com/CVE-2005-4853/): Missing authorization in n/a (critical 9.4)
- [CVE-2010-2672](https://insights.sbomify.com/CVE-2010-2672/): SQL injection in n/a (high 7.5)
- [CVE-2008-6844](https://insights.sbomify.com/CVE-2008-6844/): Privilege escalation in n/a (high 7.5)
- [CVE-2012-4053](https://insights.sbomify.com/CVE-2012-4053/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1565 is a high-severity missing authorization vulnerability in n/a, published on 6 Oct 2012. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2012-1565 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-1565/ (Markdown: https://insights.sbomify.com/CVE-2012-1565/index.md)
```

## Sources

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

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