# CVE-2009-4877: Cross-site request forgery in n/a

> Remote attackers can hijack user authentication in WebGUI via CSRF, potentially taking over accounts.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 May 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hhx8-cc3g-6wcp

## What is CVE-2009-4877?

CVE-2009-4877 is a medium-severity vulnerability in n/a, published on 26 May 2010. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in WebGUI before 7.7.14 allow remote attackers to hijack the authentication of users for unspecified requests via unknown vectors.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Plainblack Webgui.

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

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

## Is CVE-2009-4877 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2837](https://insights.sbomify.com/CVE-2005-2837/): Multiple eval injection vulnerabilities in PlainBlack Software WebGUI before 6.7.3 allow remote attackers to execute arbitrary Perl code via (high 7.5)
- [CVE-2015-1564](https://insights.sbomify.com/CVE-2015-1564/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-4877 is a medium-severity vulnerability in n/a, published on 26 May 2010. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-4877 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-4877/ (Markdown: https://insights.sbomify.com/CVE-2009-4877/index.md)
```

## Sources

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

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