Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2025-70886 — A Proof of Concept (PoC) exploit for CVE-2025-70886, a persistent denial-of-service vulnerability in Halo CMS (v2.22.4 and earlier) that allows remote attackers to crash the admin comment interface by submitting malformed payloads. | Kitploit
Tools/GitHubGitHub/howiehz/cve-2025-70886
Vulnerability AnalysisExploitationWeb Application ExploitationPenetration TestingRed TeamingArchived
GitHubhowiehz/cve-2025-70886

CVE-2025-70886

A Proof of Concept (PoC) exploit for CVE-2025-70886, a persistent denial-of-service vulnerability in Halo CMS (v2.22.4 and earlier) that allows remote attackers to crash the admin comment interface by submitting malformed payloads.

View Repository
339 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    994
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    656
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    422
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    389
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    333
  • 6

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    330

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2025-70886

A Proof of Concept (PoC) exploit for CVE-2025-70886, a persistent denial-of-service vulnerability in Halo CMS (v2.22.4 and earlier) that allows remote attackers to crash the admin comment interface by submitting malformed payloads.

Basic Information

  • Product Vendor: 凌霞软件
  • Vendor Website: https://www.lxware.cn/
  • Affected Object Type: Software / Web application
  • Affected Product: Halo CMS
  • Affected Product Versions: <= v2.22.4
  • Vulnerability type: Persistent DoS (Stored DoS) / Unhandled Exception
  • Attack type: Remote
  • Impact: Denial of Service (admin comment page returns HTTP 500 / Internal Server Error)

Vulnerability Overview

An issue in Halo v2.22.4 and earlier allows a remote attacker to cause a denial of service via a crafted payload to the public comment submission endpoint.

Details of the vulnerability

An attacker can submit a crafted/malformed comment payload (missing fields such as subjectRef.version) via the public comment submission endpoint. The malformed comment is stored and later triggers an unhandled exception when the admin comment page reads/renders it, resulting in a persistent denial of service for the comment management page until the offending record is removed or server-side validation/handling is fixed.

  • Impact: Admin comment page becomes unavailable (HTTP 500 / Internal Server Error) after a malformed comment is submitted and stored; recovery may require manual database cleanup or deletion via API.

What this repo contains

  • A workflow that boots Halo and records a result per version.
  • Minimal tooling to send a test comment request.

What the workflow does

  1. Download and start a specified Halo version.
  2. Initialize the system.
  3. Configure the comment system.
  4. Send a test request and check the comments API response.
  5. Save a per-version result and publish a final summary.

Audit results

At the end of the run, the Summary job publishes a table showing each Halo version and its status:

  • likely_vulnerable — API returned HTTP 500 during the check.
  • not_confirmed — API did not return HTTP 500.

Results: https://github.com/HowieHz/CVE-2025-70886/actions/runs/21742076721

Manual Reproduction Steps

⚠️ Warning: For authorized testing environments only

  1. Clone the PoC repository

    git clone https://github.com/HowieHz/CVE-2025-70886
    cd CVE-2025-70886
    
  2. Deploy a Halo CMS test instance

    • Follow the official Halo documentation to deploy a vulnerable version (<= v2.22.4) of Halo CMS
    • Default address: http://localhost:8090
  3. Initialize the system

    • Access the Halo console to complete the initial setup.
    • Configure the comment system:
      • Navigate to http://localhost:8090/console/settings?tab=comment
      • Ensure "Allow comments from registered users only"(仅允许注册用户评论) is disabled (If login is required to comment, you can reproduce the issue using the method described at blog instead of running the PoC script below.)
      • Ensure "Enable comments"(启用评论) is enabled
  4. Execute the PoC script (Ensure the Node.js environment is configured.)

    node src/poc.js --base-url http://localhost:8090 --payload fixtures/payload.sample.json
    

    Available options:

    • --base-url: Halo site base URL (e.g., http://localhost:8090)
    • --payload: Path to a captured, valid comment payload JSON file
    • --dry-run: Only print modified payload, do not send
    • --header: Extra header in 'Key: Value' form (repeatable)
    • --help: Show help
  5. Verify the vulnerability

    • Visit the admin comment page: http://localhost:8090/console/comments
    • If Internal Server Error (HTTP 500) appears, the vulnerability is confirmed

References

  • https://github.com/halo-dev/halo/issues/7890
  • https://howiehz.top/archives/halo-comment-payload-tweaker-en
Download Tool