Skip to main content
CVE-2025-70151VulnerabilityPublished Updated

CVE-2025-70151: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
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:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Feb 2026

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

What to do

AI-suggested

Immediate mitigation should focus on restricting file upload functionality. This includes implementing strict server-side validation of file types and extensions, allowing only safe image formats (e.g., JPEG, PNG) and rejecting any executable or script files. Employ content inspection techniques such as MIME type verification and file signature checks. Store uploaded files outside the web root or configure the web server to prevent execution of files in the uploads directory (e.g., using .htaccess rules or equivalent). Implement strong authentication and monitor for unusual upload activity. Conduct regular audits of uploaded files to detect malicious content. If patching is unavailable, consider disabling the upload functionality temporarily. Additionally, apply web application firewalls (WAFs) with rules to detect and block attempts to upload or execute PHP files in upload directories. Educate users about the risks of uploading unauthorized files and enforce the principle of least privilege for authenticated users. Finally, maintain comprehensive logging and alerting to detect exploitation attempts promptly.

Description

code-projects Scholars Tracking System 1.0 allows an authenticated attacker to achieve remote code execution via unrestricted file upload. The endpoints update_profile_picture.php and upload_picture.php store uploaded files in a web-accessible uploads/ directory using the original, user-supplied filename without validating the file type or extension. By uploading a PHP file and then requesting it from /uploads/, an attacker can execute arbitrary PHP code as the web server user.

References

Community reviews

Loading reviews…