# CVE-2013-1401: Missing authorization in n/a

> Remote attackers can add, edit, or delete poll answers and polls due to missing authorization checks in the WordPress Poll Plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m9h5-h74r-gp39

## What is CVE-2013-1401?

CVE-2013-1401 is a critical missing authorization vulnerability in n/a, published on 13 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple security bypass vulnerabilities in the editAnswer, deleteAnswer, addAnswer, and deletePoll functions in WordPress Poll Plugin 34.5 for WordPress allow a remote attacker to add, edit, and delete an answer and delete a poll.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Cardozatechnologies Wordpress Poll.

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

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

## Is CVE-2013-1401 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1400](https://insights.sbomify.com/CVE-2013-1400/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1401 is a critical missing authorization vulnerability in n/a, published on 13 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-1401 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-1401/ (Markdown: https://insights.sbomify.com/CVE-2013-1401/index.md)
```

## Sources

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

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