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

> Unauthenticated attackers can modify plugin settings via an exposed AJAX action in the WooCommerce Category Banner Management plugin.

- **Severity:** Medium 5.3 (`CVSS:3.0/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:** 31 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-wj2m-wx8r-329h

## What is CVE-2018-11579?

CVE-2018-11579 is a medium-severity missing authorization vulnerability in n/a, published on 31 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

class-woo-banner-management.php in the MULTIDOTS WooCommerce Category Banner Management plugin 1.1.0 for WordPress has an Unauthenticated Settings Change Vulnerability, related to certain wp_ajax_nopriv_ usage. Anyone can change the plugin's setting by simply sending a request with a wbm_save_shop_page_banner_data action.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Multidots Woocommerce Category Banner Management.

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

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

## Is CVE-2018-11579 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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