# CVE-2024-0909: Anonymous Restricted Content <= 1.6.2 - Protection Mechanism Bypass

> Unauthenticated attackers can access protected posts and pages via the REST API due to insufficient restrictions in the Anonymous Restricted Content plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 3 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qvp9-wwpx-gmjx

## What is CVE-2024-0909?

CVE-2024-0909 is a medium-severity vulnerability in cayenne Anonymous Restricted Content, published on 3 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Anonymous Restricted Content plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.6.2. This is due to insufficient restrictions through the REST API on the posts/pages that protections are being place on. This makes it possible for unauthenticated attackers to access protected content.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-0909?

It affects 1 product.


Products: Cayenne Anonymous Restricted Content.

## How do I fix CVE-2024-0909?

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

## Is CVE-2024-0909 being exploited?

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

## Other vulnerabilities in cayenne Anonymous Restricted Content

- [CVE-2024-11089](https://insights.sbomify.com/CVE-2024-11089/): Anonymous Restricted Content <= 1.6.5 - Unauthenticated Content Restriction Bypass to Sensitive Information Exposure (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0909 and fix it if it is affected.

What it is: CVE-2024-0909 is a medium-severity vulnerability in cayenne Anonymous Restricted Content, published on 3 Feb 2024. 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-2024-0909 in the wild and no public exploit code.

Affected product: cayenne Anonymous Restricted Content. 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-2024-0909/ (Markdown: https://insights.sbomify.com/CVE-2024-0909/index.md)
```

## Sources

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

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