basicsecurity.net
Proof, not just disclosure.
Threats / SysAid / CVE-2025-2776
CVE-2025-2776 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

SysAid On-Prem vulnerability

SysAid On-Prem contains an XML external entity (XXE) vulnerability in Server URL processing that enables administrator account takeover and unauthorized file access.

Verdict

Today item — known-exploited.

An unauthenticated attacker can exploit XXE injection in the Server URL parameter to read arbitrary files from the affected system and assume control of administrator accounts, with active exploitation confirmed in the wild.

CISA KEV Yes · 2025-07-223EPSS 0.72971 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
208 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 2025-07-22).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.72971 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: SysAid, SysAid On-Prem. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-611 XML External Entity (XXE) — weakness family: Web / client.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious XML payload embedding an external entity reference in the Server URL field to trigger XXE processing.
Business
The organization's SysAid deployment becomes a vector for data exfiltration and privilege escalation without detection.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I read sensitive configuration files and credentials from the server filesystem through XXE file inclusion techniques.
Business
Confidential system data, API keys, and database credentials are exposed to unauthorized parties.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage the XXE vulnerability to modify or inject administrator account credentials through entity manipulation.
Business
Attackers gain persistent administrative access to the SysAid platform and underlying infrastructure.
4

Data at risk — exfiltration narrative 4

Attacker
I use administrator privileges to deploy malware, exfiltrate data, or pivot to connected systems.
Business
The organization faces operational disruption, data breach liability, and potential ransomware deployment.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 208 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by VulnCheck (CNA)
  • Named finder/reporter credit (CVE.org)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • Disclosure & credit2
    Catalogued by VulnCheckCNA
    Credited with finding itSina Kheirkhah (@SinSinology)finderJake KnottfinderwatchTowrsponsor