CVE-2026-11772
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDRIMO 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,
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDRIMO CMS contains a reflected XSS vulnerability in its search functionality where the 'q' parameter is not properly sanitized. An attacker can craft a malicious URL containing JavaScript code that will execute in the victim's browser when they visit the crafted link.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- A
- Scope
- X
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm DRIMO CMS is installedLook for DRIMO CMS files on the web server. Check for typical installation directories or the presence of DRIMO-specific files such as index.php, admin/, or configuration files containing 'DRIMO' in the filename or content.Affected if The web server hosts DRIMO CMS software.
-
Locate the search functionalityIdentify pages or endpoints that contain a search feature. Common patterns include /search.php, /search.html, or a search form on the main page. Look for query parameters named 'q' in URLs.Affected if A search feature with a 'q' parameter exists on the site.
-
Test the 'q' parameter for reflected inputSubmit a benign test string such as <script>alert('XSS')</script> or "><script>alert(1)</script> as the value of the 'q' parameter in the search URL. Observe whether this string is reflected verbatim in the page response without encoding or sanitization.Affected if The input appears unescaped in the HTML response, indicating the parameter is not sanitized.
-
Check if info.php file existsLook for the file info.php in the web root directory. Attempt to access it directly via a browser (e.g., https://yourdomain.com/info.php).Affected if The info.php file is present and accessible on the server.
-
Verify the search endpoint is accessible without authenticationConfirm that the search functionality can be accessed by unauthenticated users. Attempt to access the search URL directly without logging in.Affected if The search page loads for anonymous users without requiring authentication.
A user is affected if DRIMO CMS is installed, the search functionality with the 'q' parameter is accessible, and the input is reflected without sanitization, making the info.php workaround not yet applied.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedDelete the info.php file from the server, which eliminates the attack vector. This is the recommended workaround since the product is end-of-life and will not receive official security patches.
- 1. Locate the info.php file in the DRIMO CMS installation directory.
- 2. Delete or remove the info.php file from the server.
- 3. Verify the file has been removed by attempting to access it via the browser.
- 4. Test the search functionality to confirm the XSS vulnerability is mitigated (the search should still function without the q parameter being exploitable).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11772 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11772 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data