Defensive WordPress security scanner for CVE-2026-87902 — local filesystem inspection and safe remote HTTP/HTTPS assessment.
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.
The local checker is intended to run directly on the WordPress server or on a copy of the WordPress installation.
It can inspect:
register_argc_argvopen_basedirinclude_pathpearcmd.phpwp-content/uploadsThe local checker performs read-only analysis and does not modify the installation.
The remote checker is designed for situations where you have only HTTP/HTTPS access to a WordPress site.
It can:
page-* related directoriesThe remote checker deliberately avoids:
The scripts use only the Python standard library.
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.
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.
python wp-cve-2026-87902-remote.py https://example.com
Example:
python wp-cve-2026-87902-remote.py https://wordpress.example.com
python wp-cve-2026-87902-remote.py https://example.com --timeout 15
python wp-cve-2026-87902-remote.py https://example.com --verbose
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.
The remote checker may report results such as:
PATCHEDThe detected WordPress core version is at or above the corresponding patched version.
POTENTIALLY VULNERABLEThe 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 VERSIONThe detected WordPress version belongs to an affected release line, but the remote checker could not establish the additional public precondition.
INCONCLUSIVEThe 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.
The remote checker uses exit codes that can be useful in scripts and CI/CD environments:
| Exit code | Meaning |
|---|---|
0 | No vulnerability indicator detected / patched or inconclusive-safe result |
1 | Potential vulnerability detected |
2 | Scanner error or unable to perform the assessment |
Always review the textual output in addition to the exit code.
| Capability | Local checker | Remote 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 checks | Limited | ✅ |
| 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.
Remote vulnerability detection has important limitations.
A web server normally does not expose:
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.
This project intentionally follows a read-only / non-destructive approach.
The scripts do not: