CVE-2025-2776
SysAid On-Prem versions <= 23.3.40 are vulnerable to an unauthenticated XML External Entity (XXE) vulnerability in the Server URL processing functionality, allowing for administrator account takeover and file read primitives.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. The attack involves sending specially crafted XML data in HTTP requests to the server URL processing functionality. Such XML with external entity declarations is unusual and can be detected by a WAF, but some legitimate XML might look similar, so filtering is only partly reliable. A custom WAF rule can filter XML bodies containing external entity declarations in Server URL processing requests, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.
What a custom rule would match: XML bodies containing external entity declarations in Server URL processing requests
Also consider: patch · custom WAF rule · disable DTDs in parser
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-2776 being exploited?
Yes. CVE-2025-2776 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-2776?
CVE-2025-2776 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-2776?
Yes. A fix has been recorded for CVE-2025-2776. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-2776 affect?
CVE-2025-2776 affects sysaid:sysaid. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 23.3.40
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept · 1 Nuclei template
- SysAid On-Prem <= 23.3.40 - XML External Entity · detection template · critical
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 22 Jul 2025 (SSVC 2.0.3).
timeline
- 7 May 2025Published
- 22 Jul 2025Added to CISA KEV (exploited in the wild) · 75 days (about 3 months) later
- 22 Jul 2025CISA SSVC assessment: exploitation active · same day later
- 12 Aug 2025CISA remediation due date (US federal agencies) · 21 days later
- 31 Aug 2025First proof-of-concept repository on GitHub (unvetted) · 19 days later
- 19 Nov 2025CVE record last updated · 81 days (about 3 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 348 days (about 12 months) later
- Advisorydocumentation.sysaid.com /docs/24-40-60
- Exploitlabs.watchtowr.com /sysowned-your-friendly-rce-support-ticket/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-2776
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.