Exploit catalog results

Showing 9 PoCs on this page

GitHub

Smarttfoxx/copyfail

Repository PoCStars: 11Created 2026-05-01
ExploitCVE-2026-314312 files

8.5 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A C exploit for CVE-2026-31431 that achieves local privilege escalation by corrupting the page cache of payload withheld via AF_ALG AEAD operations, then executing the modified binary to gain root.

Backdoor review

No backdoor observed in reviewed code

The repository contains a single C exploit (exploit.c) and a README.md describing a local privilege escalation PoC for CVE-2026-31431. The exploit uses AF_ALG socket operations to corrupt the page cache of payload withheld and then executes it to gain root. All code is directly aligned with the described vulnerability exploitation technique; no hidden, deceptive, or unrelated harmful behavior (such as credential theft, persistence, or remote access) is present. The shellcode payload performs only setuid(0) and execve("/bin/sh").

ClassificationExploit
Model confidence100%
AuthenticationNot required
LanguagesC
Target softwareLinux kernel (crypto/algif_aead)
Attack typeslocal privilege escalation
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact contains complete, compilable C source code that actively exploits CVE-2026-31431 to overwrite a setuid binary's page cache with shellcode and then execute it to gain root privileges. The README explicitly describes it as a 'Local privilege escalation exploit' and provides usage instructions showing a root shell.

README.md:3exploit.c:163-264

Requirements

  • Local unprivileged user access to a vulnerable Linux kernel with AF_ALG support and a setuid-root payload withheld binary.exploit.c:163-172

Observed behavior

  • Opens payload withheld, parses its ELF headers to resolve the entry point virtual address to a file offset.exploit.c:168-193
  • Creates an AF_ALG socket and binds to the 'authencesn(hmac(sha256),cbc(aes))' AEAD algorithm with a zero key.exploit.c:195-227
  • For each 4-byte chunk of the shellcode, sends AAD containing the shellcode bytes via sendmsg with MSG_MORE, splices 32 bytes from the target file's page cache as the authentication tag, and triggers decryption via recv to write controlled bytes into the page cache.exploit.c:88-161exploit.c:241-255
  • Executes the corrupted payload withheld binary, which runs the injected shellcode (setuid(0); execve("/bin/sh")) to spawn a root shell.exploit.c:261-264exploit.c:52-67
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Technique
Payload withheldThe exploit uses the CVE-2026-31431 vulnerability to escalate privileges locally. This is the stated purpose of the PoC.exploit.c:88-161exploit.c:163-265README.md:8-14
Shellcode
Payload withheldThe shellcode embedded in the exploit performs only privilege escalation to a root shell, consistent with the PoC's stated goal.exploit.c:52-67README.md:18-32
Target Binary
Payload withheldThe exploit targets a setuid-root binary to achieve privilege escalation, which is the documented attack vector for this CVE.exploit.c:42exploit.c:168exploit.c:262
Review boundaries

What the analysis did not establish

  • Evidence is limited to the supplied source files; no binary, build artifacts, or runtime output were provided or analyzed.
  • The exploit targets a specific kernel vulnerability and setuid binary; it may not work on patched kernels or systems without payload withheld.
  • Only the two text files (README.md and exploit.c) were reviewed; no binary artifacts were present or analyzed.
  • The review does not assess whether the exploit actually works or is safe to execute; it only evaluates the presence of backdoor or deceptive behavior in the supplied code.
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

Smarttfoxx/CVE-2026-29923

Repository PoCStars: 4Created 2026-01-23
WriteupCVE-2026-299231 file

3.0 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a README.md file that describes a local privilege escalation vulnerability (CVE-2026-29923) in the pstrip64.sys driver. It provides a technical analysis of the IOCTL handler, explains how arbitrary physical memory mapping can be abused to overwrite kernel structures, and outlines exploitation steps, but explicitly states that no exploit code is provided.

Backdoor review

No backdoor observed in reviewed code

The artifact is a README.md file describing a known privilege escalation vulnerability (CVE-2026-29923) in the pstrip64.sys driver. The text explains the vulnerability mechanism (arbitrary physical memory mapping via IOCTL) and outlines a theoretical exploitation method (scanning physical memory, locating EPROCESS structures, and overwriting a token). No executable code, scripts, or instructions for the reader to execute are present. The author explicitly states that no PoC code is provided. The described behavior is consistent with the documented CVE and does not exhibit backdoor or deceptive payload characteristics.

ClassificationWriteup
Model confidence95%
AuthenticationRequired
Languagesmarkdown
Target softwareEnTech Taiwan PowerStrip
Attack typesprivilege_escalation
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a technical writeup. It contains a substantive analysis of the vulnerability, including vulnerable code logic and exploitation steps, but does not include any executable exploit or scanner code. The author explicitly states that no code is provided.

README.md:26

Requirements

  • Local, low-privileged access to a system with the vulnerable pstrip64.sys driver installed.README.md:2

Observed behavior

  • The document describes the vulnerability in the IOCTL handler 0x80002008, which maps arbitrary physical memory into the calling process's address space.README.md:6
  • The document outlines a proof-of-concept exploitation method that scans physical memory for _EPROCESS structures and overwrites a process token to gain SYSTEM privileges.README.md:26-30
  • The author explicitly states that no exploit code will be made publicly available.README.md:26
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Description
Payload withheldThe README documents a legitimate vulnerability, not a backdoor. The described exploitation technique (token stealing) is a standard privilege escalation method.README.md:1-8
Code Snippet
Payload withheldSnippet illustrates the vulnerable driver logic. It is presented as documentation, not as executable instructions for the reader.README.md:11-17
Author Statement
Payload withheldConfirms that no executable PoC is included in the repository, reducing the risk of hidden malicious payloads.README.md:26
Review boundaries

What the analysis did not establish

  • The evidence consists of a single README.md file; no source code, binary, or executable artifact is included.
  • The analysis is based solely on the text description and cannot verify the accuracy of the technical claims or the existence of the described vulnerability.
  • Only the README.md file was provided; no other repository files (e.g., source code, scripts, binaries) were included in the evidence packet.
  • The analysis scope confirms 'NO_POC_CODE_IDENTIFIED' and 'NO_EXECUTABLE_SOURCE_IDENTIFIED', so the review is limited to the documentation text.
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

Smarttfoxx/CVE-2025-67263

Repository PoCStars: 1Created 2026-01-18
WriteupCVE-2025-672631 file

1.2 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a README file describing a stored XSS vulnerability (CVE-2025-67263) in Abacre Retail Point of Sale. It explains the vulnerable fields (Name, Surname) and the trigger (clicking 'Statement'), but contains no executable code, scanner, or exploit script.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists solely of a README.md file describing a stored XSS vulnerability (CVE-2025-67263) in Abacre Retail Point of Sale. The file contains no executable code, no instructions for the reviewer to perform any action, and no concealed or deceptive payload. It is a plain-text vulnerability disclosure with embedded image references.

ClassificationWriteup
Model confidence95%
AuthenticationUnknown
Languagesmarkdown
Target softwareAbacre Retail Point of Sale
Attack typesstored cross-site scripting
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a textual description of a vulnerability with no executable code. It does not contain an exploit or scanner script, only a writeup with embedded images.

README.md:1-12

Requirements

  • Access to the Clients module to insert payload into Name or Surname fields.README.md:2
  • Ability to save client details to the database.README.md:8
  • Ability to trigger the XSS by clicking the 'Statement' button.README.md:8

Observed behavior

  • The README describes a stored XSS vulnerability where a script payload is saved in the Name or Surname fields and executed when the 'Statement' button is clicked.README.md:2README.md:8
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Description
Payload withheldThe README describes a CVE and includes a sample XSS payload (<script>alert("xss 1")</script>) as part of the vulnerability explanation, not as an instruction for the reviewer.README.md:1-12
Review boundaries

What the analysis did not establish

  • The artifact contains only a README file; no exploit or scanner code is present.
  • The analysis is based solely on the supplied text; the embedded images were not inspected.
  • Only the README.md file was provided; no other files from the repository were inspected.
  • The analysis does not verify the accuracy of the described vulnerability or the safety of the linked images.
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

Smarttfoxx/CVE-2025-67261

Repository PoCStars: 1Created 2026-01-18
WriteupCVE-2025-672611 file

1.9 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a technical writeup describing a content-based blind SQL injection vulnerability (CVE-2025-67261) in Abacre Retail Point of Sale 14.0.0.396. It explains the vulnerable Search function, provides example SQL payloads, and includes screenshots showing the application's response to confirm the vulnerability. No executable exploit or scanner code is provided.

Backdoor review

No backdoor observed in reviewed code

The artifact is a single README.md file documenting a blind SQL injection vulnerability (CVE-2025-67261) in Abacre Retail Point of Sale. It contains only descriptive text, static image links, and example SQL payloads for the target application. No executable code, obfuscated content, or instructions directed at the reviewer are present. The SQL examples are standard proof-of-concept payloads consistent with the described vulnerability and do not exhibit backdoor or deceptive behavior.

ClassificationWriteup
Model confidence95%
AuthenticationUnknown
Languagesmarkdownsql
Target softwareAbacre Retail Point of Sale
Attack typessql injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README.md file that describes a vulnerability, provides example SQL injection payloads, and shows screenshots of the application's behavior. It does not contain any executable code to exploit or scan for the vulnerability; it is a technical analysis and demonstration of the issue.

README.md:1-2README.md:10-11

Requirements

  • Access to the Search function of the Orders page in Abacre Retail Point of Sale 14.0.0.396.README.md:2

Observed behavior

  • The writeup describes injecting SQL payloads into the Search function to confirm the existence of a 'Client' table and enumerate the number of records.README.md:8-11README.md:24-27
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

SQL Payload
Payload withheldExample payload demonstrating the described blind SQL injection in the target application's Search function.README.md:11
SQL Payload
Payload withheldExample payload demonstrating boolean-based blind SQL injection to confirm table row count.README.md:27
Review boundaries

What the analysis did not establish

  • The artifact contains only a README.md file; no executable code is present.
  • The analysis relies on the text description and embedded image references; the actual images are not available for inspection.
  • Review is limited to the single README.md file provided; no other repository files were inspected.
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

Smarttfoxx/CVE-2025-65321

Repository PoCStars: 2Created 2025-12-02
WriteupCVE-2025-653211 file

1.8 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a README file describing a directory traversal vulnerability (CVE-2025-65321) in the Language Sloth Discord bot. It provides a technical analysis of the vulnerable code in files.py, explains how unsanitized user input in the 'name' parameter allows path traversal, and gives example payloads. It does not contain executable exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence is a single README.md file that documents a directory traversal vulnerability (CVE-2025-65321) in a Discord bot. It contains no executable code, no instructions for the reviewer to run, and no concealed or deceptive payload. The content is a straightforward vulnerability disclosure with example payloads that illustrate the claimed flaw.

ClassificationWriteup
Model confidence95%
AuthenticationUnknown
Languagesmarkdownpython
Target softwareLanguage Sloth Discord bot
Attack typespath traversal
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README file that describes a vulnerability, provides vulnerable code snippets, and explains the attack vector. It does not contain any executable exploit code or scanner code; it is purely a technical writeup.

README.md:1-52

Requirements

  • Attacker must be able to send commands to the Discord botREADME.md:4

Observed behavior

  • The gif() and png() functions build file paths using unsanitized user input for the 'name' parameterREADME.md:2
  • The name parameter is directly interpolated into the file path without validation or sanitizationREADME.md:33
  • Example payloads show directory traversal sequences to access files outside the intended directoryREADME.md:40-48
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Documentation
Payload withheldThe README describes a path traversal vulnerability in gif() and png() functions, including code snippets and example payloads.README.md:1-52
Review boundaries

What the analysis did not establish

  • Only one file (README.md) was provided; no source code or exploit code was included.
  • The CVE record (CVE-2025-65321) was absent from the acquired CVEList dataset, so no authoritative description was available.
  • Only the README.md file was provided; no other repository files were included for review.
  • The analysis is limited to the text content of the supplied file; no binary or executable content was present.
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

Smarttfoxx/CVE-2025-65320

Repository PoCStars: 0Created 2025-10-25
WriteupCVE-2025-653201 file

1.8 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a README file describing CVE-2025-65320, a cleartext storage vulnerability in Abacre Restaurant POS. It provides a technical description of the vulnerability, references debugger output images as evidence, and lists the affected product and CWE classifications. It contains no exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists solely of a README.md file describing CVE-2025-65320, a cleartext storage vulnerability in Abacre Restaurant POS. The file contains no executable code, no instructions for the reviewer to run, and no concealed payload. It only documents the vulnerability and includes references to external images. No backdoor or deceptive behavior is present in the reviewed text.

ClassificationWriteup
Model confidence100%
AuthenticationUnknown
LanguagesMarkdown
Target softwareAbacre Restaurant Point of Sale (POS)
Attack typesCleartext Storage of Sensitive Information in Memory
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README file that provides a technical description of the vulnerability, references debugger output images, and lists CWE classifications. It contains no executable code, scripts, or instructions that constitute an exploit or scanner. It is a substantive technical analysis without exploit or scanner code, fitting the definition of a writeup.

README.md:1-32

Requirements

  • Attacker must be able to attach a debugger to the Abacre Restaurant POS process or analyze its memory dump during an activation attempt.README.md:4

Observed behavior

  • The application leaves valid device-bound license keys in process memory during an activation attempt.README.md:4
  • The keys can be obtained by attaching the process to a debugger and analyzing the process/memory dump.README.md:4
  • The obtained keys can be used to activate the software on the same machine without purchasing.README.md:4
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Documentation
Payload withheldThe README.md describes a vulnerability in a third-party application, not a backdoor or malicious payload targeting the reviewer.README.md:1-4
External Image Reference
Payload withheldThe README references external images hosted on GitHub as evidence of the vulnerability. These are not executable and were not analyzed, but their presence does not indicate a backdoor.README.md:8
Review boundaries

What the analysis did not establish

  • The artifact references debugger output images (lines 8, 10, 14, 16, 18) which are not included as text and cannot be analyzed.
  • The analysis is based solely on the README.md file; no other source code or executable files are present in the evidence.
  • External images referenced in the README were not analyzed; they are not part of the supplied text evidence.
  • Only the README.md file was provided; no other repository files were included 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

Smarttfoxx/CVE-2025-60791

Repository PoCStars: 2Created 2025-10-22
WriteupCVE-2025-607911 file

741 B

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a README file that describes CVE-2025-60791, a cleartext storage of sensitive information vulnerability in Easywork Enterprise 2.1.3.354. It explains that valid license keys remain in process memory after a failed activation and can be extracted via debugging or memory dump analysis. The file contains no executable code, only a textual description and two embedded screenshots.

Backdoor review

No backdoor observed in reviewed code

The artifact contains only a README.md file describing CVE-2025-60791 and displaying two embedded images. No executable code, scripts, commands, or deceptive payloads are present in the reviewed text. The content is purely informational documentation of a known vulnerability.

ClassificationWriteup
Model confidence95%
AuthenticationNot required
Languagesmarkdown
Target softwareEasywork Enterprise
Attack typescleartext storage of sensitive information
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README file that provides a textual description of the CVE-2025-60791 vulnerability and its exploitation method, but it does not contain any executable code, scripts, or tools to perform the exploitation or scanning. It is a technical writeup.

README.md:1-10

Requirements

  • Attach a debugger or analyze a process/memory dump of Easywork Enterprise after a failed activation attempt.README.md:4

Observed behavior

  • The artifact describes that valid device-bound license keys are left in cleartext in process memory after a failed activation attempt.README.md:4
  • The artifact includes two screenshots, but their content is not provided as text evidence.README.md:6-8
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Description
Payload withheldThe README describes the vulnerability and its impact, consistent with the associated CVE record.README.md:2-4
Embedded Image
Payload withheldImage likely shows a screenshot related to the vulnerability; no executable content is present in the text.README.md:6
Embedded Image
Payload withheldImage likely shows a screenshot related to the vulnerability; no executable content is present in the text.README.md:8
Review boundaries

What the analysis did not establish

  • The artifact contains two embedded screenshots (lines 6 and 8) whose content is not provided as text and therefore could not be analyzed.
  • The analysis is based solely on the supplied text of the README file; no other files from the repository were provided.
  • Only the README.md file was reviewed; the repository may contain other files not included in the evidence packet.
  • The content of the embedded images was not inspected; they could contain text or instructions, but no executable code.
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

Smarttfoxx/CVE-2025-45778

Repository PoCStars: 2Created 2025-07-11
Not analyzedCVE-2025-457781 file
GitHub

Smarttfoxx/OTRS-4.0.1-6.0.1-Remote-Command-Execution

Repository PoCStars: 0Created 2024-08-11
Not analyzedCVE-2017-169212 files