CVE
Otter Blocks unauthenticated stored XSS in comment links
- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.10
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.2.10.
Summary
The Otter Blocks WordPress plugin is affected. An unauthenticated user can post a comment containing a link that runs arbitrary JavaScript when clicked, for example by a logged-in administrator, because the plugin does not escape dynamic data inserted into HTML attributes.
Original description
The Otter Blocks WordPress plugin before 3.2.10 does not use URL-aware escaping when it resolves its dynamic data tags inside HTML attributes, which could allow unauthenticated users to post comments containing links that execute arbitrary JavaScript when clicked, for example by a logged-in administrator.
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.2.10.
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-123132 (Otter Blocks < 3.2.10 - Unauthenticated Stored XSS via Comment Links), 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-123132 (entry last updated 2026-11-18):
Affected:
- Unknown Otter Blocks: fixed in 3.2.10
Fixed versions: 3.2.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123132 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123132 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:
- the references on https://cve.now/CVE-2026-123132
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-123132
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-123132"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Unknown Otter Blocks
fixed in 3.2.10
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-123132 |
| Record | NVD · CVE-2026-123132 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | wpscan.com · vulnerability/eb372fd2-e3c9-4c04-87b1-ec13231cee4e |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123132
Is CVE-2026-123132 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-123132?
Otter Blocks: before 3.2.10.Source: cve.now feed data
How do I fix CVE-2026-123132?
Upgrade to a fixed version: 3.2.10.Source: cve.now feed data