Threats / Adobe / CVE-2012-0767
CVE-2012-0767
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Adobe Flash Player vulnerability
Adobe Flash Player contains a cross-site scripting (XSS) vulnerability allowing remote attackers to inject malicious web scripts or HTML code.
Verdict
Today item — known-exploited.
A reflected or stored XSS flaw in Flash Player enables attackers to execute arbitrary JavaScript in victim browsers within the context of vulnerable web applications, potentially compromising user sessions and data.
CISA KEV Yes · 2022-06-084EPSS 0.06662 (verify live)5CVSS 6.1 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-06-08).
Probability (EPSS)
EPSS 0.06662 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) · Affected: Adobe, Flash Player. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-79 Cross-site Scripting (XSS) — weakness family: Web / client.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 3765 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious URL or web page containing XSS payload targeting Flash Player's input handling.
Business
User trust in web application security is undermined when malicious scripts execute in their browser.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trick a user into visiting my crafted page or clicking a malicious link embedding the XSS payload.
Business
Customer data and session tokens become exposed to unauthorized access and theft.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute JavaScript in the victim's browser session, stealing cookies, credentials, or performing actions on their behalf.
Business
Regulatory compliance violations occur if personal or financial data is compromised through the vulnerability.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05