# CVE-2026-11772: Reflected XSS in DRIMO CMS

> Reflected XSS in DRIMO CMS allows arbitrary JavaScript execution via the search parameter, requiring mitigation by deleting info.php as the product is end-of-life.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-hm9m-vhgh-rq6m

## What is CVE-2026-11772?

CVE-2026-11772 is a medium-severity cross-site scripting vulnerability in DRIMO CMS, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

DRIMO CMS is vulnerable to Reflected XSS via q parameter in searching functionality. An attacker can prepare an URL that, when opened, results in arbitrary JavaScript execution in the victim's browser.

Product is in End Of Life phase and will not receive any updates. However, deleting info.php file mitigates the vulnerability,

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-11772 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11772 is a medium-severity cross-site scripting vulnerability in DRIMO CMS, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-11772 in the wild and no public exploit code.

Affected product: DRIMO CMS. 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-11772/ (Markdown: https://insights.sbomify.com/CVE-2026-11772/index.md)
```

## Sources

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

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