Scan report
FreshRSS / FreshRSS
Could an attacker exploit mistakes in this code?
Serious issues. Review the high-severity findings before using it.
- High
- 4
- Medium
- 78
- Low
- 0
Sources: Bandit, Semgrep, pip-audit
Does this code look like it is trying to cause harm?
Minor issues. Worth a glance, unlikely to be urgent.
- High
- 14
- Medium
- 0
- Low
- 12
Sources: YARA, ClamAV, GuardDog, dependency checker
- Likely real
- 28
- Uncertain
- 17
- Likely noise
- 63
The risk classifier rates every finding for how likely it is to be a real issue. Likely noise still counts, just much less.
What we found, in plain English
This repository has a high vulnerability score of 103.0, which means there are many insecure coding patterns that an attacker could exploit to break into the system or steal data. While the malicious-pattern score is very low at 1.0, suggesting the code does not appear to be intentionally harmful, the high vulnerability score indicates that the code contains common mistakes like using weak passwords and executing commands with user input. The scan also found several medium-risk issues, such as potential cross-site scripting vulnerabilities and overly permissive security headers, which could allow attackers to bypass protections or inject malicious scripts into the application. Although some findings are flagged as potentially malicious by automated tools, most of them stem from standard insecure practices rather than deliberate attacks, so they should be addressed through careful code review and updates to fix the underlying weaknesses before deploying the software.
Written by a local language model from the findings below. The risk scores come from the classifier, not from this summary.
Detections by engine
Score over time
Overall score each time this repository was scanned.
Findings
Highest severity first. Select a finding to see the code and what it means.
-
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/passwordUtil.php line 33
- Likely real
- Uncertain, 49% confidence
bcrypt hash detected
$hash = '$2y$04$usesomesillystringfore7hnbRJHxXVLeakoG8K30oukPsA.ztMG'; -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/phpmailer/phpmailer/src/PHPMailer.php line 1969
- Likely real
- Uncertain, 43% confidence
Executing non-constant commands. This can lead to command injection.
$mail = @popen($sendmail, 'w'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/phpmailer/phpmailer/src/PHPMailer.php line 1941
- Likely real
- Uncertain, 43% confidence
Executing non-constant commands. This can lead to command injection.
$mail = @popen($sendmail, 'w'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /cli/i18n/I18nFile.php line 85
- Likely real
- Uncertain, 43% confidence
Evaluating non-constant commands. This can lead to command injection.
$content = eval($content); -
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /app/Utils/httpUtil.php
- Likely real
- Probably noise, 1% confidence
YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /.github/workflows/tests.yml
- Likely real
- Probably noise, 1% confidence
YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Makefile
- Likely real
- Probably noise, 1% confidence
YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /CHANGELOG.md
- Likely real
- Probably noise, 1% confidence
YARA rule matched: detect_download_and_execute — Downloads a remote resource AND executes it - the actually dangerous combination, not just downloading alone
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /lib/simplepie/simplepie/src/File.php
- Likely real
- Probably noise, 1% confidence
YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /app/Utils/httpUtil.php
- Likely real
- Probably noise, 1% confidence
YARA rule matched: detect_obfuscated_string_execution — Reconstructs a string character-by-character or from hex escapes, then immediately executes it - fromCharCode/chr() alone are common in ordinary text-processing code, so this requires both the reconstruction and an execution call together
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/Dockerfile-Newest
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/Dockerfile-Arch
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /README.fr.md
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/README.md
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/entrypoint.sh
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/Dockerfile-Alpine
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/Dockerfile
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Docker/Dockerfile-Oldest
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_persistence_mechanism — Modifies a startup/scheduling location - legitimate application code essentially never does this
-
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/f.php line 69
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
touch($ico); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/f.php line 80
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
readfile($ico); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/f.php line 49
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$url = file_get_contents($txt); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/f.php line 38
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$txt_mtime = @filemtime($txt) ?: 0; -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/f.php line 37
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$ico_mtime = @filemtime($ico) ?: 0; -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/ext.php line 116
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
readfile($absolute_filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/ext.php line 108
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$mtime = @filemtime($absolute_filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 61
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
unlink('../../keys/' . $key . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 46
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
unlink('keys/' . $key . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/fever.php line 175
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$username = @file_get_contents(DATA_PATH . '/fever/.key-' . sha1(FreshRSS_Context::systemConf()->salt) . '-' . $feverKey . '.txt', false); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/http-conditional.php line 89
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
if ((!$feedMode) && (($modifScript = (int)filemtime($scriptName)) > $UnixTimeStamp)) -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/install.php line 361
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$data = is_writable(USERS_PATH . '/' . $defaultUser . '/config.php'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 29
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$canonical = @file_get_contents('keys/' . $key . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 43
- Likely real
- Yes, 55% confidence
File name based on user input risks server-side request forgery.
$hubFile = @file_get_contents('feeds/' . $canonicalHash . '/!hub.json'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/dotNotationUtil.php line 225
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($rssItem['title'] != '' || $rssItem['content'] != '' || $rssItem['link'] != '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/dotNotationUtil.php line 225
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($rssItem['title'] != '' || $rssItem['content'] != '' || $rssItem['link'] != '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/dotNotationUtil.php line 225
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($rssItem['title'] != '' || $rssItem['content'] != '' || $rssItem['link'] != '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1192
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($item['title'] != '' || $item['content'] != '' || $item['link'] != '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/fever.php line 176
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($username != false) { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/favicons.php line 70
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($iri == false) { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/favicons.php line 65
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($href == false) { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1482
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($callbackUrl == '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1409
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if (($hubFile = @file_get_contents($hubFilename)) != false) { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1370
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if (($hubFile = @file_get_contents($path . '/!hub.json')) != false) { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1192
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($item['title'] != '' || $item['content'] != '' || $item['link'] != '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1192
- Likely real
- Yes, 54% confidence
Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues
if ($item['title'] != '' || $item['content'] != '' || $item['link'] != '') { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/greader.php line 1091
- Likely real
- Yes, 53% confidence
Access-Control-Allow-Origin response header is set to "*". This will disable CORS Same Origin Policy restrictions.
header('Access-Control-Allow-Origin: *'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/query.php line 197
- Likely real
- Yes, 53% confidence
Access-Control-Allow-Origin response header is set to "*". This will disable CORS Same Origin Policy restrictions.
header('Access-Control-Allow-Origin: *'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/draggable.js line 86
- Likely real
- Uncertain, 49% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
draggableItem.insertAdjacentHTML('beforebegin', event.dataTransfer.getData('text/html')); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/draggable.js line 88
- Likely real
- Uncertain, 49% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
draggableItem.insertAdjacentHTML('afterend', event.dataTransfer.getData('text/html')); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/main.js line 1834
- Likely real
- Uncertain, 49% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
div.querySelector('.dropdown-menu-scrollable').insertAdjacentHTML('beforeend', html); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/integration.js line 26
- Likely real
- Uncertain, 48% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
event.target.closest('fieldset').insertAdjacentHTML('beforebegin', newShare); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/main.js line 867
- Likely real
- Uncertain, 48% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
div.insertAdjacentHTML('beforeend', template); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/main.js line 1187
- Likely real
- Uncertain, 48% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
div.insertAdjacentHTML('beforeend', template); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/scripts/main.js line 1837
- Likely real
- Uncertain, 48% confidence
Detection of insertAdjacentHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use insertAdjacentHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML.
datalistLabels.insertAdjacentHTML('beforeend', datalist); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/File.php line 88
- Likely real
- Uncertain, 36% confidence
Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers).
$deserialized = unserialize((string) file_get_contents($this->name), ['allowed_classes' => false]); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/MySQL.php line 274
- Likely real
- Uncertain, 36% confidence
Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers).
$feed['child'][\SimplePie\SimplePie::NAMESPACE_ATOM_10]['entry'][] = unserialize((string) $row); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/Redis.php line 119
- Likely real
- Uncertain, 36% confidence
Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers).
return unserialize($data); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/MySQL.php line 243
- Likely real
- Uncertain, 36% confidence
Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers).
$data = unserialize($row[1]); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/Memcached.php line 92
- Likely real
- Uncertain, 36% confidence
Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers).
return unserialize($data); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/Memcache.php line 96
- Likely real
- Uncertain, 36% confidence
Calling `unserialize()` with user input in the pattern can lead to arbitrary code execution. Consider using JSON or structured data approaches (e.g. Google Protocol Buffers).
return unserialize($data); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1333
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
return @unlink($this->cacheFilename()); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 61
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink('../../keys/' . $key . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 46
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink('keys/' . $key . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/install.php line 188
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink(join_path(DATA_PATH, 'config.php')); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/install.php line 161
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink(DATA_PATH . '/config.php'); //To avoid access-rights problems -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/FormAuth.php line 92
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($file_info->getPathname()); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/FormAuth.php line 77
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink(DATA_PATH . '/tokens/' . $token . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1419
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($path . '/' . $currentUser . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1357
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
return @unlink($this->lockPath); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /cli/do-install.php line 170
- Likely real
- Probably noise, 21% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink(join_path(DATA_PATH, 'config.php')); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/Minz/Configuration.php line 234
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($tmp_filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/lib_rss.php line 397
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
return unlink($dir); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /cli/db-backup.php line 25
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/lib_rss.php line 407
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/phpmailer/phpmailer/src/PHPMailer.php line 3316
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($file); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/phpmailer/phpmailer/src/PHPMailer.php line 3319
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($signed); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/phpmailer/phpmailer/src/PHPMailer.php line 3325
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($signed); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/simplepie/simplepie/src/Cache/File.php line 124
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
return unlink($this->name); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 145
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($userFilename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /p/api/pshb.php line 163
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($userFilename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /cli/export-sqlite-auto.php line 64
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
if (@unlink($old)) { -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Controllers/updateController.php line 312
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink(UPDATE_FILENAME); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Controllers/userController.php line 56
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($config_path); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 478
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($path . '.ico'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 479
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($path . '.txt'); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/Feed.php line 1346
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($this->lockPath); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Models/FormAuth.php line 37
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($token_file); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Services/ExportService.php line 173
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($zip_file); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/feverUtil.php line 76
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
return @unlink($feverKeyPath); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/httpUtil.php line 54
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($file); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/actualize_script.php line 44
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($mutexFile); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/actualize_script.php line 54
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($mutexFile); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /cli/db-restore.php line 55
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/Minz/Configuration.php line 229
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($tmp_filename); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /app/Utils/httpUtil.php line 76
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
@unlink($txt); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/Minz/Extension.php line 571
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($path); -
- Engine
- Semgrep · Pattern-based code analysis
- Counts towards
- Vulnerability
- File
- /lib/lib_rss.php line 332
- Likely real
- Probably noise, 20% confidence
Using user input when deleting files with `unlink()` is potentially dangerous. A malicious actor could use this to modify or access files they have no right to.
unlink($file); -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 8% confidence
Loose version constraint: 'stylelint-order^8.1.1' — attacker could push malicious update
stylelint-order:^8.1.1 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'eslint^10.10.0' — attacker could push malicious update
eslint:^10.10.0 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: '@stylistic/stylelint-plugin^5.3.0' — attacker could push malicious update
@stylistic/stylelint-plugin:^5.3.0 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'stylelint-config-recommended^18.0.0' — attacker could push malicious update
stylelint-config-recommended:^18.0.0 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'stylelint^17.15.0' — attacker could push malicious update
stylelint:^17.15.0 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'rtlcss^4.3.0' — attacker could push malicious update
rtlcss:^4.3.0 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'neostandard^0.14.0-next.1' — attacker could push malicious update
neostandard:^0.14.0-next.1 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'markdownlint-cli2^0.23.2' — attacker could push malicious update
markdownlint-cli2:^0.23.2 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: 'globals^17.12.0' — attacker could push malicious update
globals:^17.12.0 -
- Engine
- Dependency checker · CVEs, typosquats and risky installs
- Counts towards
- Supply chain
- File
- package.json
- Likely real
- Probably noise, 2% confidence
Loose version constraint: '@eslint/js^10.0.1' — attacker could push malicious update
@eslint/js:^10.0.1 -
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /.github/workflows/tests.yml
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version
-
- Engine
- YARA · Malware signature rules
- Counts towards
- Malicious pattern
- File
- /Makefile
- Likely real
- Probably noise, 0% confidence
YARA rule matched: detect_downloader — Downloads a remote resource - common and low-signal alone; see detect_download_and_execute for the composite version
No findings match these filters.