Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4078

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-24

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

70/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

The ITERAS plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple shortcodes (iteras-ordering, iteras-signup, iteras-paywall-login, iteras-selfservice) in all versions up to and including 1.8.2. This is due to insufficient input sanitization and output escaping in the combine_attributes() function. The function directly concatenates shortcode attribute values into JavaScript code within <script> tags using double-quoted string interpolation (line 489: '"'.$key.'": "'.$value.'"') without any escaping. An attacker can break out of the JavaScript string context by including a double-quote character in a shortcode attribute value and inject arbitrary JavaScript. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Technical summary

dbcve analysis · high confidence

The ITERAS WordPress plugin fails to sanitize shortcode attributes before embedding them into JavaScript code. The combine_attributes() function directly concatenates attribute values using double-quoted string interpolation (`'"'.$key.'": "'.$value.'"'`) without escaping double-quote characters, allowing authenticated Contributors to break out of the JS string context and inject arbitrary JavaScript.

MitigationUpdate ITERAS plugin to version 1.8.3 or later which properly escapes shortcode attributes before embedding in JavaScript contexts; alternatively, ensure all shortcode attribute inputs are escaped using appropriate JavaScript escaping functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify ITERAS plugin is installed

Navigate to WordPress admin > Plugins and look for 'ITERAS' in the list of installed plugins

Affected if ITERAS plugin appears in the plugins list
Check installed ITERAS plugin version

In Plugins list, locate ITERAS and note the version number displayed below the plugin name

Affected if Version is present and is earlier than 1.8.3 (e.g., 1.8.2, 1.8.1, etc.)
Identify if ITERAS shortcode is in use

Search posts/pages content for '[iteras' shortcode patterns, or check theme templates for do_shortcode calls referencing iteras

Affected if Any ITERAS shortcode (such as [iteras_widget], [iteras_form], etc.) is present in published content
Confirm shortcode attributes accept user input

Review the shortcode implementation or test by inserting a shortcode with custom attribute values, such as [iteras_widget id="test" value="test"]

Affected if Shortcode accepts arbitrary attribute values that get reflected in the page output

User is affected if ITERAS plugin is installed with a version before 1.8.3 and any ITERAS shortcode accepting user-supplied attributes is in use on the site.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update ITERAS plugin to version 1.8.3 or later which properly escapes shortcode attributes before embedding in JavaScript contexts; alternatively, ensure all shortcode attribute inputs are escaped using appropriate JavaScript escaping functions.

Have this fixed Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing1.0 h
Review / QA1.0 h

4.0 hours of engineering $750

Get help mitigating

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 locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-4078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4078 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-4078?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 6.4 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Remediation

Need this fixed?

Have this fixed 4 hrs · Moderate

Typical engagement from $750

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-4078 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References