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

> Remote attackers can hijack administrator sessions via CSRF to inject XSS payloads in the AskApache Firefox Adsense WordPress 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:** 2 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xpg3-mpgm-gxqh

## What is CVE-2013-6992?

CVE-2013-6992 is a medium-severity vulnerability in n/a, published on 2 Jan 2014. 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 askapache-firefox-adsense.php in the AskApache Firefox Adsense plugin 3.0 and earlier for WordPress allows remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via the aafireadcode parameter to wp-admin/options-general.php.

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

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

It affects 1 product.


Products: Askapache Firefox Adsense.

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

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

## Is CVE-2013-6992 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6992 is a medium-severity vulnerability in n/a, published on 2 Jan 2014. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-6992 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-6992/ (Markdown: https://insights.sbomify.com/CVE-2013-6992/index.md)
```

## Sources

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

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