Skip to main content
CVE-2025-9416VulnerabilityPublished

CVE-2025-9416: oitcode samarium · Cross Site Scripting

Affects oitcode samariumSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
oitcode samariumAffected
  • =0.9.0
  • =0.9.1
  • =0.9.2
  • =0.9.3
  • =0.9.4
  • =0.9.5
  • =0.9.6
Fixed in–

AI-suggested

1. Immediate mitigation should include implementing strict input validation and output encoding on all user-controllable inputs within the /cms/webpage/ Pages Image Handler component to prevent script injection. 2. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 3. Monitor web server logs for suspicious requests targeting the vulnerable endpoints to detect potential exploitation attempts. 4. Isolate or restrict access to the affected component if possible, limiting exposure. 5. Educate users and administrators about the risk of phishing or social engineering attacks leveraging this vulnerability. 6. Engage with oitcode for official patches or updates and plan for prompt deployment once available. 7. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block XSS payloads targeting the affected paths. 8. Regularly review and update security policies to include this vulnerability and ensure compliance with data protection laws.

Description

A security flaw has been discovered in oitcode samarium up to 0.9.6. This vulnerability affects unknown code of the file /cms/webpage/ of the component Pages Image Handler. The manipulation results in cross site scripting. The attack may be performed from a remote location. The exploit has been released to the public and may be exploited.

References

Community reviews

Loading reviews…