# CVE-2026-9271: KeepInMind - Dashboard Notes < 0.8.4.2 - Contributor+ Stored XSS


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-8fxh-qpf8-gq8x

## What is CVE-2026-9271?

CVE-2026-9271 is a medium-severity vulnerability in Unknown KeepInMind Dashboard Notes, published on 12 Jun 2026. 

### Official description

Vulnerability Title

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


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

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

## Is CVE-2026-9271 being exploited?

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

Public exploit code:

- WordPress KeepInMind CVE-2026-9271 Exploit - Tool detecting stored XSS in KeepInMind plugin v0.8.4.2 and below. Built by Sudeepa Wanigarathna, it simulates CSS injection to hijack admin accounts. Features safe testing, attack simulation, credential capture, bulk scanning, reporting. Essential for security researchers. (github_poc): https://github.com/CerberusMrXi/WordPress-KeepInMind-CVE-2026-9271-Exploit
- KeepInMind 0.8.4.2 -  Stored XSS (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9271 is a medium-severity vulnerability in Unknown KeepInMind Dashboard Notes, published on 12 Jun 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9271 exists.

Affected product: Unknown KeepInMind Dashboard Notes. 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-9271/ (Markdown: https://insights.sbomify.com/CVE-2026-9271/index.md)
```

## Sources

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

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