Skip to main content
Mallory
HighVulnerability

CVE-2026-18360: Stored XSS in DFIR-IRIS Custom Attributes

Published Jul 30, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.6High · v3.1
EPSS0.28%21st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-18360CWE-79 · Improper Neutralization of Input…

CVE-2026-18360 is a stored cross-site scripting vulnerability in the DFIR-IRIS web application, confirmed in version 2.4.26 and possibly affecting additional versions. The flaw resides in the custom attributes functionality, where administrators can assign attributes to object types. This feature supports an HTML input type, and insufficient output neutralization allows attacker-controlled markup or script to be stored and later rendered in the application. The malicious payload executes when affected custom attributes are loaded in normal workflows, including customer creation or editing. Successful exploitation results in arbitrary JavaScript execution in the browser of another user viewing the affected content.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation enables execution of arbitrary JavaScript in the victim's authenticated browser session within the DFIR-IRIS application context. This can support session hijacking, credential theft, unauthorized actions performed as the victim, interface manipulation, and data access available to the compromised user. If an administrator is targeted, the vulnerability can enable effective full application takeover through abuse of administrative privileges.

Mitigation

If you can’t patch tonight, do this now.

Until a fix is available, restrict or disable use of the custom attributes functionality, particularly HTML-capable attribute types, to trusted administrators only or remove that capability entirely. Apply strict output encoding for all user-supplied content rendered in the GUI and harden the Content Security Policy, including removal of unsafe-inline, as a defense-in-depth measure. Monitor for suspicious attribute content and review existing stored custom attributes for malicious payloads.

Remediation

Patch, then assume compromise.

Upgrade to a vendor-fixed release once available. The vulnerable custom attributes rendering path should be corrected by applying strict contextual output encoding or sanitization to all user-controlled data before it is rendered, especially for HTML-capable attribute types. Safer templating practices should be used consistently instead of ad hoc filtering, and the custom attributes feature should be reviewed to eliminate unsafe rendering behavior.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-18360 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-18360 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-18360?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-18360.
Is there a patch for CVE-2026-18360?
Upgrade to a vendor-fixed release once available. The vulnerable custom attributes rendering path should be corrected by applying strict contextual output encoding or sanitization to all user-controlled data before it is rendered, especially for HTML-capable attribute types.
How severe is CVE-2026-18360?
CVE-2026-18360 has a CVSS v3.1 score of 7.6 (High) and an EPSS score of 0.28% (21st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity2Community discussion across Reddit, Mastodon, and other social sources.