# CVE-2024-38775: WordPress CTX Feed plugin <= 6.5.6 - Arbitrary Options Update vulnerability

> Attackers can escalate privileges via arbitrary options update in the CTX Feed WordPress plugin, requiring an upgrade to secure the site.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-57xm-m24p-r448

## What is CVE-2024-38775?

CVE-2024-38775 is a high-severity vulnerability in WebAppick CTX Feed, published on 1 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Improper Privilege Management vulnerability in WebAppick CTX Feed allows Privilege Escalation.This issue affects CTX Feed: from n/a through 6.5.6.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2024-38775 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38775 is a high-severity vulnerability in WebAppick CTX Feed, published on 1 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38775 in the wild and no public exploit code.

Affected product: WebAppick CTX Feed. 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-38775/ (Markdown: https://insights.sbomify.com/CVE-2024-38775/index.md)
```

## Sources

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

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