# CVE-2026-65554: WordPress AnsPress – Question and answer plugin 4.4.4 - Broken Access Control vulnerability

> Subscribers can bypass access controls in the AnsPress WordPress plugin, potentially modifying data or escalating privileges.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L`)
- **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:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-wwxj-5hc7-fvp3

## What is CVE-2026-65554?

CVE-2026-65554 is a high-severity missing authorization vulnerability in lattepress AnsPress – Question and answer, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Subscriber Broken Access Control in AnsPress – Question and answer 4.4.4 versions.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-65554?


## How do I fix CVE-2026-65554?

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

## Is CVE-2026-65554 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65554 and fix it if it is affected.

What it is: CVE-2026-65554 is a high-severity missing authorization vulnerability in lattepress AnsPress – Question and answer, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65554 in the wild and no public exploit code.

Affected product: lattepress AnsPress – Question and answer. 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-2026-65554/ (Markdown: https://insights.sbomify.com/CVE-2026-65554/index.md)
```

## Sources

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

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