# CVE-2009-4232: Auth bypass in n/a

> Remote attackers can post messages with arbitrary account names in the Kide Shoutbox Joomla component due to improper authentication.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 8 Dec 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-822m-98ch-gchp

## What is CVE-2009-4232?

CVE-2009-4232 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Dec 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Kide Shoutbox (com_kide) component 0.4.6 for Joomla! does not properly perform authentication, which allows remote attackers to post messages with an arbitrary account name via an insertar action to index.php.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Jonijnm Com Kide.

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

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

## Is CVE-2009-4232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4232 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Dec 2009. 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-2009-4232 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-2009-4232/ (Markdown: https://insights.sbomify.com/CVE-2009-4232/index.md)
```

## Sources

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

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