---
title: "CVE-2026-120739: Optimole WordPress Plugin - Stored XSS"
description: "Optimole WordPress plugin <= 4.2.18 contains a stored XSS caused by insufficient input sanitization and output escaping in the 's (missing_srcsets[*][*].s)' parameter, letting unauthenticated attackers inject scripts executed by users visiting injected pages, exploit requires no authentication due to exposed HMAC signature."
url: https://panop.io/threat-heartbeat/CVE-2026-120739/
---

# CVE-2026-120739 Optimole WordPress Plugin - Stored XSS

Optimole WordPress plugin <= 4.2.18 contains a stored XSS caused by insufficient input sanitization and output escaping in the 's (missing\_srcsets\[\*\]\[\*\].s)' parameter, letting unauthenticated attackers inject scripts executed by users visiting injected pages, exploit requires no authentication due to exposed HMAC signature.

CVSS base score 7.2 /10

High

CISA KEV

Not listed

Public exploit

None known

Authentication

Not required

EPSS

0.34% chance of exploitation in 30 days

[View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-120739)

## Details

Type

Stored XSS

Impact

Stored XSS, Client Script Exec

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Published

7 November 2026

Updated

9 November 2026

Weakness

[CWE-79](https://cwe.mitre.org/data/definitions/79.html)

## Vendor fix

Update to the latest version beyond 4.2.18.

Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them.

## References

- [https://nvd.nist.gov/vuln/detail/CVE-2026-120739](https://nvd.nist.gov/vuln/detail/CVE-2026-120739)
- [https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/manager.php#L519](https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/manager.php#L519)
- [https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/rest.php#L1020](https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/rest.php#L1020)
- [https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/rest.php#L159](https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/rest.php#L159)
- [https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/tag\_replacer.php#L312](https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/tag_replacer.php#L312)
- [https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/tag\_replacer.php#L529](https://plugins.trac.wordpress.org/browser/optimole-wp/tags/4.2.17/inc/tag_replacer.php#L529)
- [https://plugins.trac.wordpress.org/changeset?reponame=&old=3784828%40optimole-wp&new=3784828%40optimole-wp](https://plugins.trac.wordpress.org/changeset?reponame=&old=3784828%40optimole-wp&new=3784828%40optimole-wp)
- [https://www.wordfence.com/threat-intel/vulnerabilities/id/5d60007c-8957-4c46-8c5c-47b7f626f0bb?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/5d60007c-8957-4c46-8c5c-47b7f626f0bb?source=cve)

[← All CVEs](https://panop.io/threat-heartbeat/)

## What this record can't tell you

- Whether you run the affected software, and where
- Whether an attacker can actually reach and exploit it
- The misconfigurations that never get a CVE number
- What it would cost the business, ranked into what to fix first

Panop answers these inside your environment, for this CVE and every other finding.

[Book a demo](https://panop.io/demo)
