Skip to content
KitploitKITPLOIT
OutilsExploitsBlog
Log in
Soumettre
OutilsExploitsBlog
Soumettre

Outils de Hacking, PenTest et Cybersécurité pour votre Arsenal de Sécurité !

Kitploit est un répertoire d'outils de hacking, de cybersécurité et de pentesting. Découvrez les dernières mises à jour des projets pour trouver des vulnérabilités, analyser des systèmes, automatiser les tests et renforcer votre sécurité.

FluxContactConfidentialité© 2026 Kitploit

Répertoire d'outils

Catégories

Voir toutes les catégories
Loading categories
CVE-2026-119977 — 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. | Kitploit
Outils/GitHubGitHub/mehmet-emir-eroglu/cve-2026-119977
Defensive ToolsVulnerability ScannersWeb Vulnerability ScannersVulnerability AnalysisConfiguration AuditingWeb Security
GitHubmehmet-emir-eroglu/cve-2026-119977

CVE-2026-119977

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.

Voir le dépôt
1il y a 12 joursPas encore vérifié
Partager
Contenu non disponible dans la langue demandée. Affichage de la version anglaise.

CVE-2026-119977 WordPress Core Detector

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.

CVE Information

  • Product: WordPress Core
  • Type: Unauthenticated remote code execution enabled by a time-of-check/time-of-use race during full-package core upgrades
  • CWE: CWE-367
  • CVSS: 8.1 High, CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Affected: upstream 4.7.0–7.1.3 across maintained historical branches; see technical analysis for exact branch limits.
  • Fixed: next patch release for each affected branch, up to WordPress 7.1.4.

See NVD, CVE.org, WordPress 7.1.4 release, Wordfence vulnerability record, and WordPress source for 7.1.3.

Technical Background

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.

Detection Methodology

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.

Detection Accuracy

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.

Features

  • Local-only read-only inspection; no network requests or PHP execution.
  • Branch-aware fixed-version checks.
  • Console and JSON reports with evidence, limitations, references, and UTC timestamp.
  • Stable exit codes for automation.

Requirements

Python 3.11 or newer. No runtime third-party dependencies. pytest, ruff, and mypy are development tools.

Installation

python -m pip install .

For development, install requirements.txt and use python -m pip install -e ..

Usage

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.

Command-Line Arguments

OptionMeaning
--targetRequired local WordPress root path
--formattext (default) or json
--outputWrite report to the specified file instead of stdout
--versionPrint tool version
--helpShow help

Network timeout/retry flags are not applicable because the detector performs no network operations.

Example Output

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.

Exit Codes

0 NOT_VULNERABLE, 1 VULNERABLE, 2 INCONCLUSIVE, 3 ERROR (including report write failure).

Testing

python -m pytest
ruff check .
ruff format --check .
mypy src

Tests use local temporary files and do not contact public targets.

CI/CD Integration

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.

Limitations

See limitations. In particular, static versions cannot prove the transient upgrade-window exposure and do not account for vendor backports.

Security Considerations

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.

References

Links in CVE Information plus the complete list embedded in JSON output.

Contributing

See CONTRIBUTING.md. Changes to version thresholds must cite authoritative release/advisory evidence and include boundary tests.

License

MIT; see LICENSE.

Télécharger l’outil

Populaires

Voir tout →

Découvrez les outils les plus utilisés par notre communauté.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 La boîte à outils OSINT ultime : graphe d'enquête, notation de confiance, familles d'alias, carte, chronologie et rapports. 49 modules, plus de 400 sites, aucune clé API requise.

    1.0k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    # Application d'exécution en un clic GhostLock (CVE-2026-43499)

    593
  • 3

    looking-glass

    anonghosty/looking-glass

    Plateforme CSIRT qui ingère les rapports Shadowserver dans MongoDB et les rejoue sous forme de cartes interactives, d'analyses, de constats, d'avis et de tableaux de bord exécutifs.

    371
  • 4

    redforge

    cybersecurity91/redforge

    Boîte à outils red team côté navigateur avec 102 outils hors ligne pour la reconnaissance, la génération de payloads, les attaques par identifiants, la cryptographie, l'encodage et le reporting d'engagement.

    336
  • 5

    ARTEX

    baarai/artex

    Plateforme autonome de tests d'intrusion multi-agents basée sur des LLM, avec agents planificateur/ouvrier, graphes d'actifs et d'exploration, enregistrement du trafic MITM et retest des vulnérabilités.

    326
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    Le système d'action pour la cybersécurité native IA—où l'intention devient une exécution gouvernée, les preuves deviennent une mémoire opérationnelle, et chaque opération améliore la suivante.

    322

Explorer tous les outils

Parcourez notre collection d'outils

Voir tous les outils →