Skip to main content
CVE-2025-56263VulnerabilityPublished Updated

CVE-2025-56263: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 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

AI-suggested

European organizations should implement immediate compensating controls while awaiting an official patch. These include restricting access to the /api/sms/upload/headImg endpoint to only trusted and necessary users, implementing strict authentication and authorization checks, and monitoring upload activity for anomalous behavior. Deploying web application firewalls (WAFs) with rules to detect and block suspicious file uploads can reduce risk. Organizations should also enforce server-side validation to restrict allowed file types and sizes, and sanitize file names and paths to prevent directory traversal. Regularly scanning the system for web shells or unauthorized files is critical. Network segmentation can limit the impact of a compromised system. Finally, organizations should maintain up-to-date backups and have an incident response plan ready to address potential exploitation.

Description

by-night sms V1.0 has an Arbitrary File Upload vulnerability. The /api/sms/upload/headImg endpoint allows uploading arbitrary files. Users can upload files of any size and type.

References

Community reviews

Loading reviews…