Skip to main content
VulnerabilityPublished Updated

CVE-2023-50090: Arbitrary File Write

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Jan 2024

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmureport2pkg:npm/ureport2Other threatsAffected
  • <=2.2.9
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate upgrade or patching: Organizations should verify if a patch or updated version of ureport2 addressing this vulnerability is available from the vendor or community and apply it promptly.
  2. Network segmentation: Restrict access to the ureport2 service to trusted internal networks or VPNs to reduce exposure to external attackers.
  3. Web application firewall (WAF): Deploy and configure a WAF with rules to detect and block suspicious POST requests targeting the saveReportFile method or unusual file write attempts.
  4. Input validation and monitoring: Implement strict input validation on parameters related to file paths and contents, and monitor logs for anomalous POST requests or file write activities.
  5. Incident response readiness: Prepare to detect and respond to exploitation attempts by enabling detailed logging, setting up alerts for suspicious activity, and having a response plan for potential compromise.
  6. Restrict file system permissions: Limit the permissions of the application user to prevent writing files outside designated safe directories, minimizing the impact of arbitrary file writes.
  7. Conduct security assessments: Perform penetration testing or code reviews focused on file handling functions to identify and remediate similar vulnerabilities.

Description

Arbitrary File Write vulnerability in the saveReportFile method of ureport2 2.2.9 and before allows attackers to write arbitrary files and run arbitrary commands via crafted POST request.

References

Community reviews

Loading reviews…