# CVE-2013-5977: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to create or modify products and inject XSS via CSRF in the Cart66 Lite plugin.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rjff-hcjj-9m74

## What is CVE-2013-5977?

CVE-2013-5977 is a medium-severity vulnerability in n/a, published on 1 Nov 2013. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Cart66Product.php in the Cart66 Lite plugin before 1.5.1.15 for WordPress allows remote attackers to hijack the authentication of administrators for requests that (1) create or modify products or conduct cross-site scripting (XSS) attacks via the (2) Product name or (3) Price description field in a product save action via a request to wp-admin/admin.php.

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

## Which versions are affected by CVE-2013-5977?

It affects 1 product.


Products: Cart66 Cart66 Lite Plugin.

## How do I fix CVE-2013-5977?

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

## Is CVE-2013-5977 being exploited?

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

Public exploit code:

- WordPress Plugin Cart66 1.5.1.14 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-5978](https://insights.sbomify.com/CVE-2013-5978/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5977 and fix it if it is affected.

What it is: CVE-2013-5977 is a medium-severity vulnerability in n/a, published on 1 Nov 2013. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-5977 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-2013-5977/ (Markdown: https://insights.sbomify.com/CVE-2013-5977/index.md)
```

## Sources

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

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