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

> Remote attackers can hijack user authentication to change 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:** 27 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j92p-xh86-8wrm

## What is CVE-2013-3477?

CVE-2013-3477 is a medium-severity vulnerability in n/a, published on 27 May 2014. 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 Related Posts by Zemanta plugin before 1.3.2 for WordPress allows remote attackers to hijack the authentication of unspecified users for requests that change settings via unknown vectors.

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

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

It affects 1 product.


Products: Zemanta Related Posts.

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

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

## Is CVE-2013-3477 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-3257](https://insights.sbomify.com/CVE-2013-3257/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2013-3476](https://insights.sbomify.com/CVE-2013-3476/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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