# CVE-2008-0182: Cross-site request forgery (CSRF) vulnerability in the Admin portlet in Liferay Portal before 4.4.0 allows remote authenticated users to per


- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Feb 2008
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-fxrw-q665-w573

## What is CVE-2008-0182?

CVE-2008-0182 is a medium-severity vulnerability in n/a, published on 4 Feb 2008. 

### Official description

Cross-site request forgery (CSRF) vulnerability in the Admin portlet in Liferay Portal before 4.4.0 allows remote authenticated users to perform unspecified actions as unspecified other authenticated users via the Shutdown message.

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

## Which versions are affected by CVE-2008-0182?

It affects 1 product.


Products: Liferay Liferay Enterprise Portal.

## How do I fix CVE-2008-0182?

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

## Is CVE-2008-0182 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1294](https://insights.sbomify.com/CVE-2009-1294/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-0178](https://insights.sbomify.com/CVE-2008-0178/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-0180](https://insights.sbomify.com/CVE-2008-0180/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-0181](https://insights.sbomify.com/CVE-2008-0181/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2008-0563](https://insights.sbomify.com/CVE-2008-0563/): Cross-site request forgery in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0182 and fix it if it is affected.

What it is: CVE-2008-0182 is a medium-severity vulnerability in n/a, published on 4 Feb 2008. 
Exploitation: There is no known exploitation of CVE-2008-0182 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-2008-0182/ (Markdown: https://insights.sbomify.com/CVE-2008-0182/index.md)
```

## Sources

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

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