Exploit catalog results

Showing 25 PoCs on this page

GitHub

Chocapikk/CVE-2026-39912

Repository PoCStars: 0Created 2026-04-09
ExploitCVE-2026-399122 files

7.6 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python script that exploits CVE-2026-39912 by sending a POST request to the loginWithMailLink endpoint to leak a magic link token, then exchanging it at the token2Login endpoint to obtain a bearer token and dump user data.

Backdoor review

No backdoor observed in reviewed code

The PoC exploit.py performs exactly the documented CVE-2026-39912 account takeover: it requests a magic link, extracts the leaked token, exchanges it for a bearer token, and dumps user data. No concealed, deceptive, or unrelated harmful behavior is present.

ClassificationExploit
Model confidence100%
AuthenticationNot required
LanguagesPython
Target softwareV2BoardXboard
Attack typesauthentication bypassinformation disclosureaccount takeover
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact contains a complete Python script (exploit.py) that actively exploits the vulnerability by sending HTTP requests to leak a token, exchange it for a bearer token, and access protected resources. The README describes it as an 'Account takeover + data dump' and provides usage examples showing exploitation.

exploit.py:1-136README.md:39-44

Requirements

  • login_with_mail_link_enable must be enabled in admin settingsREADME.md:30exploit.py:17
  • A valid registered email addressREADME.md:31exploit.py:18

Observed behavior

  • Sends an unauthenticated POST request to /api/v1/passport/auth/loginWithMailLink with a JSON body containing the target emailexploit.py:74-77
  • Extracts the magic link token from the HTTP response bodyexploit.py:82-83
  • Exchanges the leaked verify token at /api/v1/passport/auth/token2Login to obtain a bearer tokenexploit.py:89-92
  • Uses the obtained bearer token to authenticate and dump user data from multiple API endpointsexploit.py:43-56exploit.py:101-110
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThe script implements the described CVE-2026-39912 vulnerability: POST to loginWithMailLink, extract token from response, exchange at token2Login, then enumerate user endpoints.exploit.py:72-99exploit.py:101-110
Network Target
Payload withheldThe script takes a target URL and email as command-line arguments; no hardcoded exfiltration endpoint or unrelated network activity is present.exploit.py:114-118
Output Behavior
Payload withheldThe script prints or saves the obtained auth token and enumerated user data; no evidence of exfiltration to a remote server.exploit.py:125-132
Review boundaries

What the analysis did not establish

  • Only the two text files (README.md and exploit.py) were reviewed; no binary or other files exist in the artifact.
  • The review does not assess the safety of running the PoC against unauthorized targets or the legality of its use.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/CVE-2025-71243

Repository PoCStars: 4Created 2026-02-19
ExploitCVE-2025-712434 files

16.6 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python exploit for CVE-2025-71243, an unauthenticated remote code execution vulnerability in the SPIP Saisies plugin. The script injects PHP code via the `_anciennes_valeurs` parameter into a form, leveraging SPIP's template engine to execute arbitrary system commands. It includes check, single-command execution, and interactive shell modes, along with a crawler to discover vulnerable forms.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists of a README and a Python exploit script for CVE-2025-71243. The exploit script performs the advertised vulnerability check and command execution against a user-supplied target. No concealed executable behavior, persistence, credential theft, unrelated payload, or operator-directed harm was observed. The script's network activity is limited to the user-specified target URL and optional proxy.

ClassificationExploit
Model confidence98%
AuthenticationNot required
Languagespython
Target softwareSPIP Saisies plugin
Attack typesremote code executioncode injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a fully functional Python script that actively exploits CVE-2025-71243 by sending crafted HTTP requests to inject and execute arbitrary PHP code on a remote target, achieving remote code execution. It includes modes for checking vulnerability, executing single commands, and providing an interactive shell.

exploit.py:1-17exploit.py:79-80exploit.py:182-208

Requirements

  • Target must have a publicly accessible page containing a saisies-powered form (e.g., via Formidable plugin).README.md:28
  • Saisies plugin version must be between 5.4.0 and 5.11.0 inclusive.exploit.py:57

Observed behavior

  • Sends a POST request with a crafted `_anciennes_valeurs` parameter containing a PHP code injection payload that breaks out of an HTML attribute and executes arbitrary PHP.exploit.py:79-80exploit.py:184-186
  • Executes shell commands by base64-encoding them and injecting a `system(base64_decode(...))` call, then extracts the command output from the HTTP response.exploit.py:188-193
  • Provides an interactive shell loop that repeatedly prompts for commands and prints the output.exploit.py:195-208
  • Includes a crawler that starts from a sitemap page and follows internal links to automatically discover pages containing saisies forms.exploit.py:145-180
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Network Connection
Payload withheldThe exploit sends HTTP requests only to the target URL provided via the -u argument and to the optional proxy specified via --proxy. No hardcoded external hosts are contacted.exploit.py:60-70exploit.py:211-222
Command Execution
Payload withheldThe script constructs a payload that injects PHP code into the target SPIP application. The injected code executes a base64-encoded shell command provided by the user via -c or interactive input. This is the advertised exploit behavior.exploit.py:79-80exploit.py:188-193
Review boundaries

What the analysis did not establish

  • Evidence includes only README.md and exploit.py; two additional files (LICENSE and .gitignore) are omitted but are not material to classification.
  • The artifact's code was not executed; classification is based solely on static analysis of the provided source code.
  • Two files (3766 bytes) were omitted from text analysis and flagged as metadata-only; their content was not inspected.
  • The review is limited to the supplied evidence and does not assess the safety of executing the script against a real target.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/CVE-2026-24061

Repository PoCStars: 2Created 2026-01-22
ExploitCVE-2026-240614 files

8.4 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Go exploit for CVE-2026-24061 that connects to a telnetd service, injects 'USER=-f root' via the NEW-ENVIRON option to bypass authentication, and provides an interactive root shell.

Backdoor review

No backdoor observed in reviewed code

The repository contains a proof-of-concept exploit for CVE-2026-24061, a telnetd authentication bypass. The Go code (poc.go) implements the described vulnerability by sending a crafted USER environment variable to gain a root shell. No backdoor, deceptive payload, or concealed operator-directed harm was observed. The code performs only the advertised exploit behavior: connecting to a target, negotiating telnet options, injecting the malicious USER value, and providing an interactive shell if successful.

ClassificationExploit
Model confidence98%
AuthenticationNot required
LanguagesGo
Target softwareGNU Inetutils telnetd
Attack typesauthentication bypassargument injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The primary artifact poc.go contains complete code that actively exploits the vulnerability by connecting to a target, injecting a malicious environment variable to bypass authentication, and providing an interactive shell. This is exploitation, not mere detection or scanning.

poc.go:1-278README.md:39-47

Requirements

  • Target running vulnerable GNU Inetutils telnetd (versions 1.9.3 through 2.7)README.md:9
  • Network access to the target telnet portpoc.go:40-44

Observed behavior

  • Connects to a specified host and port via TCPpoc.go:44
  • Sends telnet protocol commands to negotiate NEW-ENVIRON and ENVIRON optionspoc.go:55-56
  • Injects the environment variable USER with value '-f root' to trigger authentication bypasspoc.go:54poc.go:142-153
  • Checks for absence of login prompt and presence of WILL ECHO to confirm successful bypasspoc.go:67-75
  • Executes 'id' command and verifies 'uid=' in output to confirm shell accesspoc.go:77-83
  • Provides an interactive shell session, reading commands from stdin and sending them to the targetpoc.go:92-109
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThis is the exact behavior described in the README and CVE advisory for CVE-2026-24061. It is the intended purpose of the PoC.poc.go:54poc.go:142-153poc.go:88
Target Environment
Payload withheldThe Dockerfile sets up a lab environment for testing the exploit, consistent with the README instructions. It does not contain any backdoor or unrelated payload.Dockerfile:1-36
Review boundaries

What the analysis did not establish

  • One file (docker-compose.yml) is omitted from the evidence; its content is not available for analysis.
  • The evidence does not include the output of executing the exploit; classification is based solely on static code analysis.
  • One file (docker-compose.yml) was omitted from the text evidence and not reviewed. Its metadata indicates it is a text file, but its content was not provided. Based on the README, it is expected to be a standard Docker Compose orchestration file for the lab environment.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/Windfall

Repository PoCStars: 18Created 2026-01-11
ExploitCVE-2026-2905967 files

Ruby · 427.9 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The repository 'Windfall' contains a full exploitation framework for CVE-2026-29059 (path traversal) and CVE-2026-23696 (SQL injection) in Windmill/Nextcloud Flow. It includes Python scripts (windfall_afr.py, windfall_sqli.py, windfall_nc_pivot.py) and Metasploit modules that actively exploit these vulnerabilities to leak credentials, forge JWTs, and achieve remote code execution.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists of documentation and Metasploit module source code for a publicly disclosed path traversal and SQL injection exploit (CVE-2026-29059, CVE-2026-23696) targeting Windmill/Nextcloud Flow. All reviewed files describe or implement the expected exploit behavior: reading arbitrary files, leaking credentials, forging JWTs, and achieving remote code execution on the target. No concealed backdoor, unrelated payload, or operator-directed harm beyond the stated exploit was observed.

ClassificationExploit
Model confidence95%
AuthenticationNot required
Languagespythonruby
Target softwareWindmillNextcloud Flow
Attack typespath traversalsql injectioncredential leakprivilege escalationremote code execution
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact includes Metasploit modules (windmill_path_traversal_rce.rb, windmill_sqli_rce.rb) that actively exploit vulnerabilities to achieve remote code execution. The README describes these as 'exploits' and provides usage examples for obtaining shells. The code is intended to exercise the vulnerability, not merely detect it.

README.md:128-130metasploit/modules/exploits/linux/http/windmill_path_traversal_rce.rb:17-21metasploit/modules/exploits/linux/http/windmill_sqli_rce.rb:18-22

Requirements

  • Target running vulnerable Windmill (v1.309.0 - v1.603.2) or Nextcloud Flow (v1.0.0 - v1.2.2)README.md:23-24
  • Network access to the target's Windmill API endpointREADME.md:195

Observed behavior

  • Sends crafted HTTP requests with path traversal sequences (e.g., '../') to the vulnerable get_log_file endpoint to read arbitrary files like /etc/passwd.README.md:294
  • Leaks credentials by reading /proc/1/environ for SUPERADMIN_SECRET, windmill_users_config.json for tokens, or PostgreSQL data files for jwt_secret.README.md:140-144
  • Uses leaked credentials or forged JWT to authenticate to the Windmill API and execute arbitrary commands via the job execution feature, achieving remote code execution.metasploit/modules/exploits/linux/http/windmill_path_traversal_rce.rb:115-117
  • The SQL injection module authenticates as a low-privileged user, exploits a SQLi in the addowner endpoint to extract jwt_secret, forges an admin JWT, and escalates privileges to superadmin for RCE.metasploit/modules/exploits/linux/http/windmill_sqli_rce.rb:147-165
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThis is the documented vulnerability exploitation path; no hidden behavior detected.README.md:107-110metasploit/modules/exploits/linux/http/windmill_path_traversal_rce.rb:121-124
Exploit Behavior
Payload withheldMatches the documented attack chain; no evidence of exfiltration to an attacker-controlled destination beyond the module's normal operation.metasploit/modules/exploits/linux/http/windmill_path_traversal_rce.rb:134-145
Exploit Behavior
Payload withheldThe module executes attacker-supplied commands on the target; this is the stated purpose of the exploit.metasploit/modules/exploits/linux/http/windmill_path_traversal_rce.rb:115-117
Exploit Behavior
Payload withheldDocumented authenticated SQLi attack chain; no hidden queries or data exfiltration beyond the described escalation.metasploit/modules/exploits/linux/http/windmill_sqli_rce.rb:147-165
Opsec Technique
Payload withheldDescribed as an OPSEC feature to remove forensic evidence; this is part of the exploit's self-destruct mechanism, not a backdoor.README.md:263-275
Review boundaries

What the analysis did not establish

  • Only 8 of 67 files in the repository were provided as text evidence. The actual Python exploit scripts (windfall_afr.py, windfall_sqli.py, windfall_nc_pivot.py) and other Metasploit module files are not included in the selected text.
  • The evidence packet reports complete_artifact_coverage as false, indicating that not all files from the repository were analyzed.
  • 59 files (344,110 bytes) were classified as unclassified or binary and were not inspected; their content is unknown.
  • Only 8 of 67 total files were provided as readable text; the remaining files could contain additional code or configuration not reviewed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/CVE-2025-68926

Repository PoCStars: 5Created 2026-01-04
ExploitCVE-2025-689266 files

24.0 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A Go-based exploit for CVE-2025-68926 that connects to a RustFS gRPC service, authenticates using the hardcoded token 'payload withheld', and performs privileged operations including server information disclosure, disk discovery, volume listing, and recursive file system exploration with file content retrieval.

Backdoor review

No backdoor observed in reviewed code

The repository contains a Go-based proof-of-concept exploit for CVE-2025-68926. The code connects to a RustFS gRPC service using a hardcoded token, then enumerates disks, volumes, directories, and reads file contents. No backdoor, deceptive payload, or concealed operator-directed harm was observed. The exploit performs only the advertised vulnerability demonstration.

ClassificationExploit
Model confidence98%
AuthenticationNot required
LanguagesGo
Target softwareRustFS
Attack typesauthentication bypassinformation disclosuredata access
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The code actively exploits the hardcoded token vulnerability to authenticate and perform privileged operations (ServerInfo, ListVolumes, ListDir, ReadAll) on a target RustFS instance. It is self-described as an 'Exploit' and includes a main function that executes the full exploitation chain when run with a target host and port.

main.go:496-532main.go:506README.md:5

Requirements

  • Network access to a vulnerable RustFS gRPC service portmain.go:121-123
  • Knowledge of the hardcoded token 'payload withheld'main.go:27

Observed behavior

  • Establishes an unencrypted gRPC connection to the target host and portmain.go:121-123
  • Authenticates to the gRPC service by setting the 'authorization' metadata header to the hardcoded token 'payload withheld'main.go:128main.go:179
  • Calls the ServerInfo RPC method to retrieve and decode server properties (MsgPack-decoded base64 data)main.go:208-237
  • Discovers available disks from the ServerInfo response or falls back to a default listmain.go:239-275
  • Lists volumes on each discovered disk via the ListVolumes RPC methodmain.go:305-335
  • Recursively explores directories on each volume using ListDir and reads file contents via ReadAll, printing JSON data or file sizesmain.go:386-439main.go:362-384
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Hardcoded Credential
Payload withheldThe exploit uses the publicly known hardcoded token to authenticate to the target gRPC service, consistent with the CVE description.main.go:27main.go:128main.go:179
Exploit Behavior
Payload withheldThe exploit calls ServerInfo, ListVolumes, ListDir, and ReadAll RPC methods to discover and exfiltrate data from the target. This matches the stated CVE impact of unauthenticated file read/write operations.main.go:208-237main.go:305-335main.go:337-360main.go:362-384
Review boundaries

What the analysis did not establish

  • Two files (docker-compose.yml and Dockerfile) are omitted from the evidence, so the lab setup referenced in the README cannot be fully verified.
  • The evidence does not include the actual execution output or confirmation that the exploit was tested against a live target.
  • Two files (docker-compose.yml and Dockerfile) were omitted from the text evidence and not reviewed; they may contain additional configuration but are not expected to alter the backdoor assessment.
  • Binary files were not present in the evidence.
  • The review is limited to static analysis of the provided source code; runtime behavior was not observed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/CVE-2025-67494

Repository PoCStars: 6Created 2025-12-10
ExploitCVE-2025-674945 files

21.2 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Automated Python exploit for CVE-2025-67494 that performs unauthenticated SSRF against ZITADEL Login UI V2, captures a leaked Bearer token via an out-of-band webhook, and uses the token to enumerate the ZITADEL Management API.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists of a README, a Python exploit script, and a project configuration file for CVE-2025-67494. The exploit script performs SSRF against a ZITADEL instance, retrieves a leaked Bearer token via a payload withheld OOB channel, and uses that token to query the ZITADEL Management API. All behavior is consistent with the documented exploit flow and targets the stated vulnerable service. No concealed executable behavior, persistence mechanisms, credential exfiltration to an attacker-controlled destination beyond the documented OOB webhook, or unrelated payloads were observed.

ClassificationExploit
Model confidence100%
AuthenticationNot required
Languagespython
Target softwareZITADEL
Attack typesSSRFcredential-leakageapi-enumeration
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact contains a complete, automated Python script (exploit.py) that actively exploits CVE-2025-67494 by sending a crafted request to trigger SSRF, capturing a leaked token, and using it to access protected API resources. The README explicitly describes it as an 'Automated exploit' and provides usage instructions for running the exploit against a target.

README.md:1-3exploit.py:1-4exploit.py:264-337

Requirements

  • Target ZITADEL instance running a vulnerable version (4.0.0-rc.1 through 4.7.0) with the Login UI V2 accessible.README.md:10-11
  • Outbound internet access from the attacker machine to payload withheld for OOB token capture.exploit.py:23

Observed behavior

  • Creates a payload withheld URL to receive out-of-band HTTP requests.exploit.py:20-33
  • Sends an unauthenticated GET request to /ui/v2/login with a malicious x-zitadel-forward-host header pointing to the payload withheld domain.exploit.py:93-106
  • Polls payload withheld API to retrieve the SSRF-induced request and extracts the leaked Bearer token from the Authorization header.exploit.py:35-87
  • Uses the stolen Bearer token to query ZITADEL Management API endpoints (IAM info, org info, users, projects, members, domains).exploit.py:309-333
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThe exploit sends a request with the x-zitadel-forward-host header to trigger SSRF, polls payload withheld for the leaked Bearer token, and uses it to query the ZITADEL Management API. This matches the described vulnerability and exploit purpose.exploit.py:93-106exploit.py:35-68exploit.py:70-87exploit.py:108-128exploit.py:130-177
External Service Usage
Payload withheldThe script creates a payload withheld URL to receive the SSRF callback and extract the Bearer token. This is a standard OOB technique for blind SSRF exploitation and is explicitly documented in the README.exploit.py:20-33README.md:141-143
Dependency
Payload withheldThe script imports from pwn import log, which is part of the payload withheld library commonly used in CTF and exploit development for logging. It is a legitimate dependency for this type of tool.exploit.py:11pyproject.toml:8
Review boundaries

What the analysis did not establish

  • Two files (Dockerfile, docker-compose.yml) are present in the repository but not included in the text evidence; their content is not analyzed.
  • The evidence does not include execution output or verification that the exploit works against a live target.
  • Two files (docker-compose.yml and Dockerfile) were omitted from the text evidence and not reviewed. Their content could contain unrelated behavior, but the provided exploit script and README show no backdoor indicators.
  • Binary content was not present in the evidence packet.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/malware_analysis_react2shell

Repository PoCStars: 3Created 2025-12-09
WriteupCVE-2025-5518211 files

53.5 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A technical analysis report detailing a supply chain attack where a CVE-2025-55182 scanner was backdoored to download and execute HTA malware from py-installer.cc. The report describes the backdoor code, malware behavior, IOCs, and detection rules, but contains no executable exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence is a payload withheld describing a backdoor in a separate repository (niha0wa/React2shell-scanner). The reviewed artifact itself contains no executable code, no backdoor, and no deceptive payload. The report documents malicious behavior in an external tool but does not perform any harmful actions.

ClassificationWriteup
Model confidence100%
AuthenticationNot required
LanguagesMarkdown
Target softwarereact-server-dom-webpackreact-server-dom-turbopackreact-server-dom-parcelReact2shell-scanner
Attack typessupply chain attackbackdoorinformation stealercryptocurrency wallet stealer
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README.md containing a detailed technical analysis report. It describes backdoor code and malware behavior but does not include any executable exploit or scanner code. The report itself is a writeup.

README.md:1-765

Requirements

  • Victim must clone and execute the backdoored React2shell-scanner repository.README.md:5

Observed behavior

  • The report describes a backdoor function _initialize_runtime_environment() that executes mshta.exe with a remote URL upon import.README.md:79-93
  • The report analyzes a multi-stage HTA malware that collects system information, targets cryptocurrency wallets, and propagates via USB.README.md:129-358
  • The report provides YARA and Sigma detection rules for the backdoor and malware.README.md:549-576
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Documentation
Payload withheldThe artifact is a text report describing a backdoor in an external repository. It contains no executable code or instructions to run a PoC.README.md:1-765
Review boundaries

What the analysis did not establish

  • Only the README.md file was provided; 10 other files in the repository were omitted.
  • The analysis is based solely on the report's claims; no executable code was inspected or executed.
  • Only the README.md file was provided; 10 other files in the repository were omitted from the evidence packet. The analysis scope confirms no executable source was identified in the artifact.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/CVE-2025-34299

Repository PoCStars: 4Created 2025-11-19
ExploitCVE-2025-342995 files

11.1 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python exploit for CVE-2025-34299 that achieves remote code execution on Monsta FTP by uploading a PHP reverse shell via the vulnerable downloadFile endpoint and triggering it.

Backdoor review

No backdoor observed in reviewed code

The exploit code performs the documented CVE-2025-34299 attack: it starts a malicious FTP server, uploads a PHP reverse shell payload to the target Monsta FTP instance, and triggers execution. No concealed backdoor, unrelated payload, or operator-directed harm beyond the stated exploit was observed.

ClassificationExploit
Model confidence100%
AuthenticationNot required
Languagespython
Target softwareMonsta FTP
Attack typesarbitrary file uploadremote code execution
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact contains a complete Python script (exploit.py) that actively exploits CVE-2025-34299 by uploading a PHP reverse shell payload and executing it to gain remote code execution, which is the definition of an exploit.

exploit.py:1-178README.md:1-7

Requirements

  • Target running Monsta FTP <= 2.11 with accessible API endpointREADME.md:1
  • Attacker must be able to run a malicious FTP server reachable by the targetexploit.py:65-88
  • Attacker must have a listener reachable by the target for reverse shellexploit.py:30-63

Observed behavior

  • Starts a malicious FTP server hosting a PHP reverse shell payloadexploit.py:65-88
  • Sends an unauthenticated POST request to the Monsta FTP API to download the payload from the malicious FTP server to a web-accessible pathexploit.py:108-132
  • Triggers the uploaded PHP file via HTTP GET to execute the reverse shell and self-deleteexploit.py:140-148
  • Establishes an interactive reverse shell using pwntoolsexploit.py:52-63
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Reverse Shell Payload
Payload withheldThe payload is a standard PHP reverse shell that connects back to the attacker-controlled listener. It is generated dynamically with attacker-supplied lhost and lport.exploit.py:72
Listener
Payload withheldThe listener is the attacker's endpoint for receiving the reverse shell connection. It is a standard component of the documented exploit.exploit.py:30-63
Malicious Ftp Server
Payload withheldThe FTP server is used to deliver the malicious PHP file to the vulnerable Monsta FTP instance via the downloadFile action. This is the core of the documented exploit.exploit.py:65-88
Review boundaries

What the analysis did not establish

  • Two files (lab/ directory contents) are omitted from the evidence; the Dockerfile and docker-compose.yml are not included, but the exploit logic is fully present in the provided text files.
  • Two files (lab/Dockerfile, lab/docker-compose.yml) were omitted from the text evidence; their content was not reviewed.
  • Binary content was not present in the evidence.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Chocapikk/CVE-2025-34152

Repository PoCStars: 5Created 2025-08-07
Not analyzedCVE-2025-341521 file
GitHub

Chocapikk/CVE-2025-5777

Repository PoCStars: 7Created 2025-07-08
Not analyzedCVE-2025-57772 files
GitHub

Chocapikk/CVE-2025-32463-lab

Repository PoCStars: 1Created 2025-07-06
Not analyzedCVE-2025-324633 files
GitHub

Chocapikk/CVE-2025-32432

Repository PoCStars: 10Created 2025-04-26
Not analyzedCVE-2025-324324 files
GitHub

Chocapikk/CVE-2023-30258

Repository PoCStars: 2Created 2025-03-16
Not analyzedCVE-2023-302582 files
GitHub

Chocapikk/CVE-2024-56145

Repository PoCStars: 47Created 2024-12-20
Not analyzedCVE-2024-561457 files
GitHub

Chocapikk/CVE-2024-8672

Repository PoCStars: 13Created 2024-12-02
Not analyzedCVE-2024-86722 files
GitHub

Chocapikk/CVE-2024-9474

Repository PoCStars: 45Created 2024-11-19
Not analyzedCVE-2024-94744 files
GitHub

Chocapikk/CVE-2024-45519

Repository PoCStars: 138Created 2024-10-05
Not analyzedCVE-2024-455194 files
GitHub

Chocapikk/CVE-2024-8504

Repository PoCStars: 44Created 2024-09-14
Not analyzedCVE-2024-8503CVE-2024-85044 files
GitHub

Chocapikk/CVE-2024-8517

Repository PoCStars: 16Created 2024-09-06
Not analyzedCVE-2024-85176 files
GitHub

Chocapikk/CVE-2024-7954

Repository PoCStars: 13Created 2024-08-10
Not analyzedCVE-2024-79548 files
GitHub

Chocapikk/CVE-2024-36401

Repository PoCStars: 88Created 2024-07-30
Not analyzedCVE-2024-364016 files
GitHub

Chocapikk/CVE-2024-34102

Repository PoCStars: 48Created 2024-06-28
Not analyzedCVE-2024-341023 files
GitHub

Chocapikk/CVE-2024-4577

Repository PoCStars: 35Created 2024-06-09
Not analyzedCVE-2024-45773 files
GitHub

Chocapikk/CVE-2024-5084

Repository PoCStars: 9Created 2024-05-27
Not analyzedCVE-2024-2024CVE-2024-50843 files
GitHub

Chocapikk/CVE-2024-29269

Repository PoCStars: 17Created 2024-05-19
Not analyzedCVE-2024-292695 files