Quick.Cart reflected XSS and authenticated RCE vulnerabilities
OpenSolution Quick.Cart v6.7 contains reflected XSS and authenticated RCE vulnerabilities allowing code execution via file upload and path traversal.
Sourcecert.pl — open the original
What to check
- Applies to
- The 2 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
CERT Polska coordinated disclosure of two vulnerabilities in OpenSolution Quick.Cart e-commerce software. CVE-2025-67683 is a reflected cross-site scripting vulnerability exploitable via a crafted URL containing malicious JavaScript in the sSort parameter. CVE-2025-67684 is a more critical authentication-required vulnerability combining local file inclusion, path traversal, and inadequate file upload validation that permits privileged attackers to upload and execute arbitrary PHP code, achieving remote code execution on the hosting server.
Version 6.7 was confirmed vulnerable through testing. The vendor was notified early in the disclosure process but did not provide information about affected version ranges or remediation timelines. Other versions remain untested and may also be vulnerable. Organizations running Quick.Cart should assume risk until vendor patches are available.
The vulnerabilities were responsibly reported by researcher Arkadiusz Marta through CERT Polska's coordinated vulnerability disclosure program.
Mentioned in this report
Detection guidance
PHP Webshell File Written by Web Server Process
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects a PHP file being created within a web application's upload or media directory by a web server or PHP process, consistent with exploitation of file upload validation flaws such as CVE-2025-67684 to plant a webshell. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: PHP Webshell File Written by Web Server Process
logsource:
category: file_event
product: windows
detection:
selection:
Image|endswith:
- \httpd.exe
- \php-cgi.exe
- \php-fpm.exe
- \w3wp.exe
- \nginx.exe
TargetFilename|contains:
- \upload\
- \uploads\
- \media\
- \files\
TargetFilename|endswith:
- .php
- .phtml
- .php5
filter:
TargetFilename|contains:
- \vendor\
- \wp-content\plugins\
condition: selection and not filter
falsepositives:
- Legitimate CMS or plugin update processes writing PHP files to upload directories
- Developer deployment scripts pushing PHP application code via the web server account
level: high
tags:
- attack.t1505.003
- attack.t1190
id: 834f565d-e82e-5fa7-8b96-562125368e49
status: experimental
author: Vorant
Web Server Process Spawning Command Shell (Possible Webshell Execution)
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects a web server or PHP interpreter process spawning a command shell or scripting engine, a common post-exploitation pattern after uploading and executing a PHP webshell via an RCE vulnerability like CVE-2025-67684. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: Web Server Process Spawning Command Shell
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- \httpd.exe
- \php-cgi.exe
- \php-fpm.exe
- \w3wp.exe
- \nginx.exe
selection_child:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \pwsh.exe
- \bash.exe
- \wscript.exe
- \cscript.exe
condition: selection_parent and selection_child
falsepositives:
- Legitimate web application administration scripts invoking system utilities
- Scheduled maintenance tasks triggered through a web management interface
level: high
tags:
- attack.t1190
- attack.t1505.003
id: fcf1a389-fc76-50e7-a05a-bd05721ede81
status: experimental
author: Vorant
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://cert.pl/en/posts/2026/01/CVE-2025-67683
Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs