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

> Remote attackers can hijack user sessions to modify Easy AdSense Lite plugin settings via CSRF, requiring user interaction.

- **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:** 5 May 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-qc4r-rw92-6xvw

## What is CVE-2013-2702?

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

### Official description

Cross-site request forgery (CSRF) vulnerability in the Easy AdSense Lite plugin before 6.10 for WordPress allows remote attackers to hijack the authentication of arbitrary users for requests that modify this plugin's settings.

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

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

It affects 1 product.


Products: Thulasidas Easy-Adsense-Lite.

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

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

## Is CVE-2013-2702 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-2702 is a medium-severity vulnerability in n/a, published on 5 May 2013. 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-2013-2702 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-2013-2702/ (Markdown: https://insights.sbomify.com/CVE-2013-2702/index.md)
```

## Sources

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

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