Skip to content

CVE-2024-38226

Is CVE-2024-38226 real, exploitable, or a false positive? Here's the community verdict.

Community verdict: No field verdicts yet. Be the first practitioner to weigh in.

signals

public sources

Exploited in wild
Yes
CISA KEV · Sep 10, 2024
Public exploit
None known
Metasploit/EDB/PoC
Base severity
7.3 High
CVSS
Exploitation prob.
3%
FIRST EPSS
Weakness
CWE-693
CWE

Confirmed exploited in the wild. Patch this first, regardless of the base score.

cisa ssvc

CISA Vulnrichment · assessed

Exploitation
Active
in the wild
Automatable
No
at scale
Technical impact
Total
on success

CISA decision, by how critical the affected system is to you:

  • low impact → Track
  • medium impact → Attend
  • high impact → Act

Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗

baseline read

auto · not a community verdict

Real — exploited in the wild

CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.

Based on CISA KEV

Confirm or dispute →
Affected:Microsoft

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Microsoft Publisher Security Feature Bypass Vulnerability

NVD only has a brief summary for this one. The community fills in the real-world detail below.

Published · Added to CISA KEV (same day)

Embed this verdict
TruePositive verdict for CVE-2024-38226
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2024-38226/badge.svg)](https://www.truepositive.app/cve/CVE-2024-38226)
HTML
<a href="https://www.truepositive.app/cve/CVE-2024-38226"><img src="https://www.truepositive.app/cve/CVE-2024-38226/badge.svg" alt="TruePositive verdict for CVE-2024-38226"></a>

Live badge that updates automatically as the community verdict changes.

timeline

  1. CISA SSVC assessment · exploitation: active
  2. Published by NVD
  3. Added to VulnCheck KEV · reported exploited in the wild
  4. Added to CISA KEV · confirmed exploited in the wild

Score and exploit changes tracked since .

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    Microsoft Publisher Protection Mechanism Failure Vulnerability — Microsoft Publisher contains a protection mechanism failure vulnerability that allows attacker to bypass Office macro policies used to block untrusted or malicious files. Listed in the CISA KEV catalog (added 2024-09-10) — confirmed exploited in the wild, not theoretical. FIRST EPSS puts the chance of exploitation in the next 30 days at ~3%. Treat it as real and prioritize remediation over triage.

  • 0
    Remediation · TruePositive EditorialCurated

    Required action for Microsoft Publisher: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. CISA set a federal remediation due date of 2024-10-01. After patching, verify the vulnerable path is no longer reachable before closing the finding.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-693.