# CVE-2009-4929: Missing authorization in n/a

> Remote attackers can change arbitrary user passwords in TotalCalendar due to missing administrative authentication checks on the user management page.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f2r2-9848-78f4

## What is CVE-2009-4929?

CVE-2009-4929 is a high-severity missing authorization vulnerability in n/a, published on 9 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

admin/manage_users.php in TotalCalendar 2.4 does not require administrative authentication, which allows remote attackers to change arbitrary passwords via the newPW1 and newPW2 parameters.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2009-4929?

It affects 1 product.


Products: Sweetphp Totalcalender.

## How do I fix CVE-2009-4929?

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

## Is CVE-2009-4929 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4929 exists.

Public exploit code:

- TotalCalendar 2.4 - Remote Password Change (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-4929 and fix it if it is affected.

What it is: CVE-2009-4929 is a high-severity missing authorization vulnerability in n/a, published on 9 Jul 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-4929 exists.

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-2009-4929/ (Markdown: https://insights.sbomify.com/CVE-2009-4929/index.md)
```

## Sources

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

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