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

> Remote attackers can modify administrator activation status without authentication by manipulating parameters in approve.php.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-w466-q2rw-4mm2

## What is CVE-2012-4926?

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

### Official description

approve.php in Img Pals Photo Host 1.0 does not authenticate requests, which allows remote attackers to change the activation of administrators via the u parameter in an (1) app0 (disable) or (2) app1 (enable) action.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Imgpals Img Pals Photo Host.

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

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

## Is CVE-2012-4926 being exploited?

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

Public exploit code:

- ImgPals Photo Host 1.0 - Admin Account Disactivation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4925](https://insights.sbomify.com/CVE-2012-4925/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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