CVE-2026-32361
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Marketing Fire Editorial Calendar editorial-calendar allows DOM-Based XSS.This issue affects Editorial Calendar: from n/a through <= 3.9.0.
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 confidenceA DOM-based Cross-Site Scripting (XSS) vulnerability exists in the Marketing Fire Editorial Calendar plugin (editorial-calendar) version 3.9.0 and below. The vulnerability stems from improper neutralization of input during web page generation, allowing malicious JavaScript to be executed in the victim's browser via the DOM.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify the Editorial Calendar plugin versionAccess your WordPress admin panel, navigate to Plugins > Installed Plugins, and locate the 'Marketing Fire Editorial Calendar' (editorial-calendar) plugin. Note the installed version number displayed.Affected if The installed version is 3.9.0 or lower.
-
Confirm the plugin is activeIn the same Plugins page, verify whether the Editorial Calendar plugin is currently activated. A DOM-based XSS can only be triggered when the vulnerable plugin code is loaded in the browser.Affected if The plugin is active and running.
-
Inspect plugin JavaScript for unsafe DOM manipulationAccess the plugin files via file manager or FTP. Navigate to the plugin directory and examine JavaScript files (*.js) for patterns where user-supplied data is inserted into the DOM without proper encoding. Look for uses of innerHTML, document.write, outerHTML, or insertAdjacentHTML with variables that could contain untrusted input.Affected if JavaScript files contain DOM manipulation operations that process URL parameters, form inputs, or AJAX responses without using context-aware encoding or safe methods like textContent.
-
Identify untrusted input sinks in the plugin codeSearch the plugin JavaScript for common XSS sinks: functions that accept HTML, eval(), setTimeout(), setInterval(), or template literals used with raw user input. Trace back whether these sinks receive data from URL parameters (like location.hash, location.search, or document.referrer), AJAX responses, or stored data.Affected if The plugin processes input from untrusted sources and passes it directly to DOM update functions without sanitization.
Your environment is affected if the Marketing Fire Editorial Calendar plugin version is 3.9.0 or below, the plugin is active, and its JavaScript code contains DOM manipulation that processes untrusted input without proper output encoding.
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.
From vendor dataFix requires identifying and sanitizing the vulnerable JavaScript code path that processes untrusted input without proper output encoding. Implement context-aware output encoding or use safe DOM manipulation methods to prevent script injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32361 — 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-32361 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