Drupal Icon API stored XSS in menu link title wrapper class
- Exploited
- No known exploitation
- Fix
- Fixed in 7.x-1.1
- Who is exposed
- Not reported
Summary
A stored cross-site scripting flaw in the Icon API: Menu submodule of Drupal Icon API lets a user with the "administer menu icons" permission inject script through the Title Wrapper Class field. The script runs in the browser of anyone who interacts with the affected menu link, which can lead to session theft and account hijacking.
Written by a model
Original description
A stored cross-site scripting (XSS) vulnerability exists in the Icon API: Menu submodule of the Drupal 7 Icon API module. When a menu item is configured with the Title Wrapper option enabled, the value of the Title Wrapper Class field is output directly into an HTML attribute without sanitization or escaping. A user with the "administer menu icons" permission can inject a payload such as title" onmouseover="alert(document.cookie) that is rendered verbatim on every page displaying the affected menu item, executing arbitrary JavaScript in the browser of any user who interacts with the menu link. This can lead to session theft, account hijacking, and further attacks against site users.
This issue affects Icon API 7.1.0.
What to do
Upgrade to a fixed version: 7.x-1.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-16132 (Drupal Icon API (Icon API: Menu) Stored XSS via unsanitized Title Wrapper Class), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-16132 (entry last updated 2026-11-20):
Affected:
- Drupal Icon API: from 7.x-1.0, fixed in 7.x-1.1
Fixed versions: 7.x-1.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-16132 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-16132 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.herodevs.com/vulnerability-directory/cve-2026-16132
- https://d7es.tag1.com/security-advisories/icon-api-less-critical-cross-site-scripting
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-16132
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-16132"}.Affected versions
- iconFrom 7.x-1.0 · fixed in 7.x-1.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-16132 |
| Other links 2 | |
| Link | herodevs.com · vulnerability-directory/cve-2026-16132 |
| Link | d7es.tag1.com · security-advisories/icon-api-less-critical-cross-site-scripting |
Questions about CVE-2026-16132
Is CVE-2026-16132 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-16132?
icon: from 7.x-1.0 before 7.x-1.1.
Source: cve.now feed data
How do I fix CVE-2026-16132?
Upgrade to a fixed version: 7.x-1.1.
Source: cve.now feed data
Related
- CVE-2026-107249Block AJAX - Highly critical - PHP object injection - SA-CONTRIB-2026-192
- CVE-2026-110176File Force Download for Drupal 7 Access Bypass via Unconditional Download Headers
- CVE-2026-19030CAPTCHA for Drupal 7 exposes login validation feedback after failed CAPTCHA
- CVE-2026-107251Entity Reference Manager (Merge entities) - Critical - Access bypass - SA-CONTRIB-2026-194
- CVE-2026-107257Actstream - Critical - Access bypass - SA-CONTRIB-2026-198
- CVE-2026-96389Xray Audit - Moderately critical - Access bypass - SA-CONTRIB-2026-206
No corrections so far. Something wrong on this page? Report an error.