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
wp-cve-2026-87902-checker — Defensive WordPress security scanner for CVE-2026-87902 — local filesystem inspection and safe remote HTTP/HTTPS assessment. | Kitploit
Tools/GitHubGitHub/abatsakidis/wp-cve-2026-87902-checker
Defensive ToolsReconnaissanceVulnerability ScannersWeb Vulnerability ScannersVulnerability AnalysisConfiguration AuditingInformation GatheringWeb Security
Share
Misconfiguration
GitHubabatsakidis/wp-cve-2026-87902-checker

wp-cve-2026-87902-checker

Defensive WordPress security scanner for CVE-2026-87902 — local filesystem inspection and safe remote HTTP/HTTPS assessment.

View Repository
121 month agoNot yet reviewed

WP-CVE-2026-87902 Checker

A lightweight, read-only security checker for identifying indicators associated with CVE-2026-87902 in WordPress installations.

The project provides two complementary Python tools:

  • wp-cve-2026-87902-check.py — local checker for a WordPress installation with filesystem access.
  • wp-cve-2026-87902-remote.py — remote, passive checker that evaluates a publicly accessible WordPress site using HTTP/HTTPS only.

Security note: This project is designed for defensive security assessment. It does not attempt exploitation, remote code execution, file modification, or destructive testing.


Features

Local checker

The local checker is intended to run directly on the WordPress server or on a copy of the WordPress installation.

It can inspect:

  • WordPress core version
  • WordPress themes and relevant directories
  • PHP configuration
  • register_argc_argv
  • open_basedir
  • include_path
  • Presence of pearcmd.php
  • Suspicious files in WordPress directories
  • Executable-like files inside wp-content/uploads
  • Additional unexpected files in core directories
  • WordPress core file integrity using the official WordPress checksum API
  • Optional WP-CLI information when WP-CLI is available

The local checker performs read-only analysis and does not modify the installation.

Remote checker

The remote checker is designed for situations where you have only HTTP/HTTPS access to a WordPress site.

It can:

  • Detect whether the target appears to be running WordPress
  • Passively identify the WordPress version when publicly exposed
  • Compare the detected version with known patched versions
  • Detect the active WordPress theme when possible
  • Check common publicly accessible page-* related directories
  • Check the public status of common WordPress endpoints
  • Produce a final assessment without sending exploit payloads

The remote checker deliberately avoids:

  • LFI/traversal payloads
  • Remote code execution
  • File uploads
  • File creation or modification
  • Command execution
  • Destructive testing

Requirements

  • Python 3.9+
  • Internet access for the remote checker
  • No third-party Python packages are required

The scripts use only the Python standard library.


Installation

Clone the repository:

git clone https://github.com/YOUR-USERNAME/wp-cve-2026-87902-checker.git
cd wp-cve-2026-87902-checker

No pip install step is required.


Local Checker

Usage

Run the checker against a local WordPress directory:

python wp-cve-2026-87902-check.py /path/to/wordpress

For example:

python wp-cve-2026-87902-check.py C:\xampp\htdocs\wordpress

or on Linux:

python3 wp-cve-2026-87902-check.py /var/www/html

If WP-CLI is installed and available, the checker can use it for additional WordPress information.


Remote Checker

Basic usage

python wp-cve-2026-87902-remote.py https://example.com

Example:

python wp-cve-2026-87902-remote.py https://wordpress.example.com

Custom timeout

python wp-cve-2026-87902-remote.py https://example.com --timeout 15

Verbose output

python wp-cve-2026-87902-remote.py https://example.com --verbose

Ignore TLS certificate verification

For controlled testing environments with a self-signed certificate:

python wp-cve-2026-87902-remote.py https://example.local --insecure

Use --insecure only when you understand the TLS implications.


Assessment states

The remote checker may report results such as:

PATCHED

The detected WordPress core version is at or above the corresponding patched version.

POTENTIALLY VULNERABLE

The checker detected an affected WordPress version together with public indicators associated with the vulnerability precondition.

This is an indicator, not proof of exploitability.

AFFECTED CORE VERSION

The detected WordPress version belongs to an affected release line, but the remote checker could not establish the additional public precondition.

INCONCLUSIVE

The information exposed by the target is insufficient to make a reliable remote assessment.

A remote scan should therefore not be interpreted as a full vulnerability assessment.


Exit codes

The remote checker uses exit codes that can be useful in scripts and CI/CD environments:

Exit codeMeaning
0No vulnerability indicator detected / patched or inconclusive-safe result
1Potential vulnerability detected
2Scanner error or unable to perform the assessment

Always review the textual output in addition to the exit code.


Local vs Remote

CapabilityLocal checkerRemote checker
WordPress version✅✅ When publicly detectable
Filesystem inspection✅❌
PHP configuration✅❌
pearcmd.php detection✅❌
Upload directory inspection✅❌
Core checksum verification✅❌
WP-CLI information✅ Optional❌
Public endpoint checksLimited✅
Theme detection✅✅ When publicly detectable
Requires server/filesystem access✅❌
Exploitation❌❌
File modification❌❌

The two scripts serve different purposes. The local checker provides deeper visibility, while the remote checker is intentionally limited to information that can be obtained safely over HTTP/HTTPS.


Limitations

Remote vulnerability detection has important limitations.

A web server normally does not expose:

  • its filesystem structure
  • PHP configuration
  • arbitrary WordPress files
  • private theme directories
  • installed plugin metadata in a reliable way
  • server-side command execution capabilities

Therefore, a remote HTTP checker cannot provide the same level of confidence as a local inspection.

In particular, the remote checker does not prove exploitability.

A result of INCONCLUSIVE does not mean that the installation is vulnerable or safe. It means that the required information was not publicly observable.

For the most reliable assessment, run the local checker with access to the actual WordPress installation.


Security Model

This project intentionally follows a read-only / non-destructive approach.

The scripts do not:

Download Tool

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.

    732
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    506
  • 3

    ARTEX

    baarai/artex

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

    405
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    342
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    261
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259

Explore all tools

Browse our collection of tools

View all tools →