
Read-only local detector that compares a WordPress core version declaration against affected and fixed branches for CVE-2026-119977, reporting VULNERABLE, NOT_VULNERABLE, or INCONCLUSIVE with JSON output.
Read-only local assessment of a WordPress Core installation for upstream code affected by CVE-2026-119977. It reads the version declaration without executing PHP and does not probe a live website or trigger an update.
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSee NVD, CVE.org, WordPress 7.1.4 release, Wordfence vulnerability record, and WordPress source for 7.1.3.
The published description attributes the flaw to predictable, web-accessible staging paths used while a full-package core upgrade is underway. Exploitation is timing-dependent. The detector does not test that race and cannot establish whether a particular server was in the upgrade window.
The tool reads wp-includes/version.php under the supplied installation root and compares the declared upstream version to published branch-specific affected/fixed versions. An affected upstream version is reported as VULNERABLE to indicate affected code. It is not proof of current exploitability. A patched upstream branch version yields NOT_VULNERABLE for this CVE's upstream code. Missing, unknown, or unlisted versions are INCONCLUSIVE; invalid/unreadable paths are ERROR. Full details and backport caveats are in methodology and limitations.
Positive findings require a local version string in a published affected range. The decision is strong for that upstream version declaration, but it does not validate file authenticity or runtime state. Negative findings mean the declared upstream patch is at or beyond the published fix only. Downstream backports, custom builds, version masking, modifications, and a current upgrade window are not verified.
Python 3.11 or newer. No runtime third-party dependencies. pytest, ruff, and mypy are development tools.
python -m pip install .
For development, install requirements.txt and use python -m pip install -e ..
python -m cve_detector --target /srv/www/wordpress
python -m cve_detector --target C:\sites\wordpress --format json --output report.json
The target must be the WordPress installation root, containing wp-includes/version.php.
| Option | Meaning |
|---|---|
--target | Required local WordPress root path |
--format | text (default) or json |
--output | Write report to the specified file instead of stdout |
--version | Print tool version |
--help | Show help |
Network timeout/retry flags are not applicable because the detector performs no network operations.
Illustrative only; timestamps and paths vary:
CVE-2026-119977 VULNERABLE
Target: /srv/www/wordpress
Summary: Upstream WordPress 7.1.3 falls within the affected range for its release line.
Method: Compare local upstream version against published WordPress fixed-version branches
Confidence: high for upstream version; not runtime exploitability
NOT_VULNERABLE indicates a fixed upstream branch version; INCONCLUSIVE indicates insufficient version evidence; ERROR indicates the path could not be assessed. JSON has the same fields: cve, target, status, summary, verification_method, confidence, observations, limitations, references, and timestamp.
0 NOT_VULNERABLE, 1 VULNERABLE, 2 INCONCLUSIVE, 3 ERROR (including report write failure).
python -m pytest
ruff check .
ruff format --check .
mypy src
Tests use local temporary files and do not contact public targets.
GitHub Actions runs tests and static checks on pushes and pull requests. Run the command against an authorized mounted installation in an operational workflow and treat exit code 2/3 as requiring review.
See limitations. In particular, static versions cannot prove the transient upgrade-window exposure and do not account for vendor backports.
Use only on installations you own or are authorized to assess. The tool reads one local text file and does not modify the target. Reports include the supplied target path; protect report files as appropriate.
Links in CVE Information plus the complete list embedded in JSON output.
See CONTRIBUTING.md. Changes to version thresholds must cite authoritative release/advisory evidence and include boundary tests.
MIT; see LICENSE.