# CVE-2023-6279: Woostify Sites Library < 1.4.8 - Subscriber+ Arbitrary Options Update to DoS

> Authenticated users can update arbitrary blog options via an unprotected AJAX action, potentially causing a denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2024
- **Updated:** 2 Jun 2025
- **Also known as:** GHSA-9xv5-7pc9-8rr3

## What is CVE-2023-6279?

CVE-2023-6279 is a high-severity missing authorization vulnerability in Unknown Woostify Sites Library, published on 29 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Woostify Sites Library WordPress plugin before 1.4.8 does not have authorisation in an AJAX action, allowing any authenticated users, such as subscriber to update arbitrary blog options and set them to 'activated' which could lead to DoS when using a specific option name

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-6279?

It affects 1 product.


Products: Woostify Sites Library.

## How do I fix CVE-2023-6279?

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

## Is CVE-2023-6279 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6279 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6279 and fix it if it is affected.

What it is: CVE-2023-6279 is a high-severity missing authorization vulnerability in Unknown Woostify Sites Library, published on 29 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6279 exists.

Affected product: Unknown Woostify Sites Library. 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-2023-6279/ (Markdown: https://insights.sbomify.com/CVE-2023-6279/index.md)
```

## Sources

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

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