Exploit catalog results

Showing 5 PoCs on this page

GitHub

ajansha/CVE-2025-60374

Repository PoCStars: 0Created 2025-10-10
WriteupCVE-2025-603741 file

5.1 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A technical writeup describing a stored XSS vulnerability (payload withheld) in Perfex CRM's chatbot. It provides HTML/JavaScript payload examples as proof-of-concept snippets and discusses mitigation strategies, but contains no executable exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The artifact is a README.md documentation file describing payload withheld, a stored XSS vulnerability in Perfex CRM. It contains no executable code, no concealed payloads, and no instructions for the reviewer to perform harmful actions. The provided PoC examples are standard XSS demonstrations consistent with the described vulnerability.

ClassificationWriteup
Model confidence100%
AuthenticationRequired
Languagesmarkdownhtmljavascriptphp
Target softwarePerfex CRM
Attack typesstored cross-site scripting (xss)
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README.md file that provides a detailed technical analysis of payload withheld, including vulnerability description, impact, proof-of-concept payload snippets, and mitigation guidance. It does not contain any standalone executable script, scanner, or automated exploitation tool. The PoC snippets are illustrative HTML/JavaScript fragments embedded in a markdown document, not functional exploit or scanner code.

README.md:1-155

Requirements

  • Attacker must be authenticated with low privileges to submit a chat message.README.md:32
  • A victim user must view the chat conversation containing the stored payload.README.md:15

Observed behavior

  • The writeup describes injecting HTML/JavaScript payloads into chat messages that are stored and later executed in other users' browsers.README.md:15
  • Example payloads include an image onerror handler, a button onclick handler, an iframe, a meter onmouseover handler, and a cookie-stealing fetch request.README.md:68-98
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Documentation
Payload withheldThe file documents a stored XSS vulnerability in Perfex CRM chatbot, including PoC examples and mitigation advice.README.md:1-155
Review boundaries

What the analysis did not establish

  • Only one file (README.md) was provided; no other repository files were inspected.
  • The artifact is a static markdown document; no dynamic behavior or execution context was observed.
  • The PoC payloads are presented as code blocks within the writeup and are not part of a runnable script.
  • Only the README.md file was provided; no other repository files were included in the evidence packet.
  • The analysis scope is limited to the supplied text; any binary or other files in the repository were not 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

ajansha/CVE-2025-60375

Repository PoCStars: 0Created 2025-10-10
WriteupCVE-2025-603751 file

2.5 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a technical writeup describing an authentication bypass vulnerability in PerfexCRM. It details the vulnerability, impact, reproduction steps, and mitigation, but contains no exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The artifact is a single README.md file that documents a known payload withheld authentication bypass vulnerability in Perfex CRM. It contains no executable code, no instructions for the reviewer to run, and no concealed payloads. The content is a straightforward vulnerability advisory describing the issue, impact, reproduction steps, and mitigation.

ClassificationWriteup
Model confidence100%
AuthenticationNot required
Languagesenglish
Target softwarePerfexCRM
Attack typesauthentication bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README.md file containing a technical advisory with a summary, impact, reproduction steps, and mitigation for payload withheld. It does not contain any executable code, scripts, or commands that constitute an exploit or scanner. It is a substantive technical analysis, classifying it as a writeup.

README.md:1-52

Requirements

  • Ability to send HTTP requests to the admin login endpoint.README.md:20

Observed behavior

  • The writeup describes a method to bypass authentication by sending empty username and password parameters to the login endpoint, resulting in unauthorized access to user accounts, including administrative accounts.README.md:13README.md:25-27
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Documentation
Payload withheldThe file is a human-readable advisory describing an authentication bypass in Perfex CRM. It includes reproduction steps that involve manipulating HTTP requests, which is normal exploit documentation for this class of vulnerability.README.md:1-52
Review boundaries

What the analysis did not establish

  • The evidence packet contains only a single README.md file. No exploit or scanner code is present in the repository snapshot.
  • Only the README.md file was reviewed; no other files exist in the repository snapshot.
  • The review does not assess the validity or safety of the described vulnerability or its reproduction steps against a live system.
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

ajansha/CVE-2025-60378

Repository PoCStars: 0Created 2025-10-09
WriteupCVE-2025-603781 file

9.4 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a security advisory writeup for CVE-2025-60378, a stored HTML injection vulnerability in RISE Ultimate Project Manager & CRM. It describes the vulnerability, affected components, impact, and mitigation steps. It includes example HTML payloads and step-by-step reproduction instructions but contains no executable exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The artifact is a single payload withheld file documenting CVE-2025-60378, a stored HTML injection vulnerability in RISE CRM. It contains no executable code, no concealed payloads, and no instructions for the reviewer to perform harmful actions. The content is purely descriptive, providing vulnerability details, impact analysis, and mitigation guidance.

ClassificationWriteup
Model confidence100%
AuthenticationRequired
Languagesmarkdown
Target softwareRISE Ultimate Project Manager & CRM
Attack typesstored html injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a detailed technical writeup describing a vulnerability, its impact, and reproduction steps. It contains no executable code, scripts, or automated scanning logic. The 'Proof of Concept' section provides manual instructions and example HTML payloads but does not constitute an exploit or scanner.

README.md:1-213

Requirements

  • Authenticated user with invoice/message creation permissions in RISE CRMREADME.md:100-101
  • RISE CRM version prior to 3.9.4README.md:20-21

Observed behavior

  • Describes injecting HTML payloads into invoice line items, client notes, and messaging modulesREADME.md:15
  • Provides example HTML payloads for phishing, image tracking, and misleading linksREADME.md:81-126
  • Outlines manual steps to reproduce the vulnerability and verify HTML rendering in emails, PDFs, and chatREADME.md:103-145
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Documentation Only
Payload withheldThe entire artifact consists of a single Markdown file with no executable code, scripts, or binary payloads.README.md:1-213
Contact Information
Payload withheldAuthor contact information is present but does not constitute backdoor behavior.README.md:181
Review boundaries

What the analysis did not establish

  • Evidence consists of a single payload withheld file; no source code, scripts, or binaries are present.
  • The artifact is a static document; no dynamic behavior or execution context is available.
  • The 'Proof of Concept' section contains only manual steps and example HTML snippets, not functional exploit or scanner code.
  • Only the payload withheld file was provided; no other repository files were included for review.
  • Binary files were flagged as metadata-only and not analyzed, but none were 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

ajansha/CVE-2025-55903

Repository PoCStars: 0Created 2025-10-09
WriteupCVE-2025-559031 file

7.0 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A technical writeup describing a stored HTML injection vulnerability (payload withheld) in PerfexCRM. The document details the vulnerability, affected components, impact, and step-by-step reproduction instructions, but contains no executable exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The artifact is a single README.md file documenting payload withheld, a stored HTML injection vulnerability in PerfexCRM. The file contains no executable code, no obfuscated payloads, and no instructions for the reader to perform actions that would compromise their own system. All described steps are standard vulnerability reproduction procedures against a remote target application.

ClassificationWriteup
Model confidence100%
AuthenticationRequired
LanguagesMarkdown
Target softwarePerfexCRM
Attack typesHTML 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 provides a detailed technical analysis of payload withheld, including vulnerability description, impact, and manual reproduction steps. It contains no executable code, scripts, or automated scanning logic; the 'PoC Steps' are purely descriptive instructions for a human operator. This constitutes a writeup.

README.md:1-174

Requirements

  • Authenticated user with invoice creation permissions in PerfexCRMREADME.md:86-87

Observed behavior

  • Describes injecting HTML payloads into invoice description and billing address fields, which are stored and rendered in client-facing emails and PDFs without escaping.README.md:96-128
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Documentation
Payload withheldThe entire file describes a stored HTML injection vulnerability in PerfexCRM, including reproduction steps, impact, and mitigation.README.md:1-174
Review boundaries

What the analysis did not establish

  • Only one file (README.md) was provided; no source code, exploit scripts, or scanner code was included.
  • The artifact's own analysis routing classified it as 'NO_POC_CODE_IDENTIFIED'.
  • Only the README.md file was provided; no other repository files were inspected.
  • Binary files were flagged but not analyzed; none were identified in the artifact inventory.
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

ajansha/shellshock

Repository PoCStars: 0Created 2024-05-10
Not analyzedCVE-2014-6271CVE-2014-71693 files