# CVE-2018-11580: Missing authorization in n/a

> Any logged-in user can create unlimited posts due to missing capability checks, enabling denial of service and content spamming.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 31 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pg4h-w7vr-xpj3

## What is CVE-2018-11580?

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

### Official description

An issue was discovered in mass-pages-posts-creator.php in the MULTIDOTS Mass Pages/Posts Creator plugin 1.2.2 for WordPress. Any logged in user can launch Mass Pages/Posts creation with custom content. There is no nonce or user capability check, so anyone can launch a DoS attack against a site and create hundreds of thousands of posts with custom content.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-11580?

It affects 1 product.


Products: Multidots Mass Pages\/Posts Creator.

## How do I fix CVE-2018-11580?

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

## Is CVE-2018-11580 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11580 and fix it if it is affected.

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

## Sources

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

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