# CVE-2016-10996: Missing authorization in n/a

> The OptinMonster WordPress plugin allows unauthorized access to shortcodes due to a nonce leak, enabling security bypass.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-83fm-966g-68w9

## What is CVE-2016-10996?

CVE-2016-10996 is a medium-severity missing authorization vulnerability in n/a, published on 20 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The optinmonster plugin before 1.1.4.6 for WordPress has incorrect access control for shortcodes because of a nonce leak.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2016-10996?

It affects 1 product.


Products: Optinmonster Optinmonster.

## How do I fix CVE-2016-10996?

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

## Is CVE-2016-10996 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-39341](https://insights.sbomify.com/CVE-2021-39341/): OptinMonster <= 2.6.4 Unprotected REST-API Endpoints (high 8.2)
- [CVE-2023-0772](https://insights.sbomify.com/CVE-2023-0772/): Popup Builder by OptinMonster < 2.12.2 - Subscriber+ Arbitrary Post Content Disclosure (medium 6.5)
- [CVE-2024-4045](https://insights.sbomify.com/CVE-2024-4045/): Cross-site scripting in Popup Builder & Popup Maker for WordPress – OptinMonster Email Marketing and Lead Generation (medium 6.4)
- [CVE-2021-39325](https://insights.sbomify.com/CVE-2021-39325/): OptinMonster <= 2.6.0 Reflected Cross-Site Scripting (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10996 and fix it if it is affected.

What it is: CVE-2016-10996 is a medium-severity missing authorization vulnerability in n/a, published on 20 Sep 2019. 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-2016-10996 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-2016-10996/ (Markdown: https://insights.sbomify.com/CVE-2016-10996/index.md)
```

## Sources

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

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