CVE-2025-4632
Improper limitation of a pathname to a restricted directory vulnerability in Samsung MagicINFO 9 Server version before 21.1052 allows attackers to write arbitrary file as system authority.
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? Yes. Path traversal sends `../` sequences in the request, which WAF rules catch, including the common encodings.
Also consider: canonical path validation
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-4632 being exploited?
Yes. CVE-2025-4632 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-4632?
CVE-2025-4632 is rated Critical with a CVSS score of 9.8. 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-4632?
Yes. A fix has been recorded for CVE-2025-4632. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-4632 affect?
CVE-2025-4632 affects samsung:magicinfo_9_server. 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< 21.1052
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: 2 GitHub proofs of concept · 1 Nuclei template
- Samsung MagicINFO 9 Server - File Upload & Remote Code Execution · 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
- total
Assessed by CISA 20 Aug 2025 (SSVC 2.0.3).
timeline
- 13 May 2025Published
- 22 May 2025Added to CISA KEV (exploited in the wild) · 9 days later
- 4 Jun 2025First proof-of-concept repository on GitHub (unvetted) · 13 days later
- 12 Jun 2025CISA remediation due date (US federal agencies) · 8 days later
- 20 Aug 2025CISA SSVC assessment: exploitation active · 69 days (about 2 months) later
- 26 Feb 2026CVE record last updated · 191 days (about 6 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
- Linksecurity.samsungtv.com /securityUpdates#SVP-MAY-2025
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-4632
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.