CVE-2026-14281 Checker

A lightweight, Windows-friendly Python security checker for identifying WordPress installations that may be affected by CVE-2026-14281.

The tool performs passive, non-destructive checks. It does not exploit the vulnerability, create accounts, modify privileges, or alter the target website.

For authorized security testing only. Only scan websites and systems that you own or have explicit permission to assess.

Features

🔎 Detects WordPress indicators
🔌 Detects the affected plugin
🏷️ Attempts to identify the installed plugin version
📄 Checks the plugin's public readme.txt
🛡️ Determines whether the detected version falls within the known affected range
🪟 Designed to work correctly on Windows CMD and PowerShell
🎨 Windows-compatible colored terminal output using Colorama
🌐 Optional HTTP/HTTPS proxy support
📊 JSON output for automation and CI/CD workflows
⏱️ Configurable HTTP timeout
🚫 No exploit requests
🚫 No account creation
🚫 No privilege modification
🚫 No OTP bypass attempts

CVE Information

Field	Details
CVE	CVE-2026-14281
Product	Automation Web Platform – Notifications and OTP for WooCommerce, Advanced Country Code
Affected versions	≤ 4.8.6
Known fixed version	4.8.7+
Scanner type	Passive / Non-destructive

The checker uses the detected plugin version to determine whether the installation falls within the known affected version range.

A result of POTENTIALLY VULNERABLE means that the detected version falls within the affected range. It is not a substitute for a full security assessment.

Requirements

Python 3.9+
Internet/network access to the target
requests
colorama

Supported operating systems:

Windows 10 / 11
Linux
macOS

Installation

Clone the repository:

git clone https://github.com/YOUR-USERNAME/CVE-2026-14281-checker.git
cd CVE-2026-14281-checker

Install dependencies:

py -m pip install -r requirements.txt

On Linux/macOS:

python3 -m pip install -r requirements.txt

Basic Usage

Windows:

py CVE-2026-14281-check.py https://example.com

Linux/macOS:

python3 CVE-2026-14281-check.py https://example.com

You can also provide a hostname without the scheme:

py CVE-2026-14281-check.py example.com

The checker will normalize it automatically.

Example Output

╔══════════════════════════════════════════════════════╗
║          CVE-2026-14281 SAFE CHECKER                 ║
║                                                      ║
║       WordPress Plugin Vulnerability Scanner         ║
╚══════════════════════════════════════════════════════╝

[*] Checking: https://example.com
[*] Mode: Passive / Non-destructive

Target: https://example.com
HTTP status: 200
WordPress: Detected
Plugin: Detected
Version: 4.8.6
Version source: readme.txt
Confidence: high
CVE status: POTENTIALLY VULNERABLE

Notes:
  • WordPress indicators detected.
  • Plugin readme.txt is accessible.
  • Version 4.8.6 is within the affected range <= 4.8.6.

[!] WARNING: Potentially vulnerable version detected.
[!] Recommended action: update the plugin and investigate the installation.

Command-Line Options

Timeout

Change the HTTP timeout:

py CVE-2026-14281-check.py https://example.com --timeout 20

Default:

10 seconds

Proxy

Useful when inspecting traffic through Burp Suite or another authorized HTTP proxy:

py CVE-2026-14281-check.py https://example.com --proxy http://127.0.0.1:8080

JSON Output

For automation or integration with other security tools:

py CVE-2026-14281-check.py https://example.com --json

Example:

{
  "target": "https://example.com",
  "reachable": true,
  "wordpress_detected": true,
  "plugin_detected": true,
  "version": "4.8.6",
  "version_source": "readme.txt",
  "vulnerable": true,
  "confidence": "high",
  "http_status": 200,
  "notes": [
    "WordPress indicators detected.",
    "Plugin readme.txt is accessible.",
    "Version 4.8.6 is within the affected range <= 4.8.6."
  ]
}

Disable Colors

If output is redirected to another program or terminal:

py CVE-2026-14281-check.py https://example.com --no-color

Exit Codes

The checker provides useful exit codes for scripting and CI/CD environments.

Code	Meaning
`0`	Target is not identified as vulnerable
`1`	Potentially vulnerable version detected
`2`	Error or vulnerability status could not be determined
`130`	User interrupted the scan

Example in Windows:

py CVE-2026-14281-check.py https://example.com

if %ERRORLEVEL% EQU 1 echo Potential vulnerability detected

How Detection Works

The checker does not attempt to exploit CVE-2026-14281.

Instead, it performs several passive checks:

1. WordPress detection

The homepage is inspected for common WordPress indicators such as:

wp-content
wp-includes
wp-json
WordPress generator metadata

2. Plugin detection

The response is inspected for references to the affected plugin directory.

3. Version detection

The checker attempts to determine the installed version from:

Plugin asset URLs
Public readme.txt

4. Version assessment

If a version is identified, it is compared against the known affected range.

Version <= 4.8.6
        │
        ├── YES → Potentially vulnerable
        │
        └── NO  → Outside known affected range

Important: False Positives and False Negatives

No passive version checker can guarantee that a target is secure.

Possible limitations include:

Plugin assets may be cached.
Version information may be hidden.
readme.txt may be inaccessible.
A security plugin may block requests.
A reverse proxy/WAF may modify responses.
The plugin may be installed but not publicly detectable.
A backported security fix may exist without a version change.
A detected version may not accurately represent the code currently running.

Therefore:

UNKNOWN does not mean secure, and NOT IN AFFECTED VERSION RANGE does not constitute a complete security assessment.

For confirmed remediation, verify the installed plugin directly from the WordPress administration environment or package/filesystem information.

Safe by Design

This project intentionally avoids active exploitation.

It does not:

create WordPress users
assign administrator privileges
modify existing accounts
attempt OTP bypasses
send exploit payloads
modify plugin settings
upload files
execute commands on the target
delete or alter data

The purpose is vulnerability identification, not exploitation.

Project Structure

CVE-2026-14281-checker/
│
├── CVE-2026-14281-check.py
├── requirements.txt
├── README.md
├── LICENSE
└── .gitignore

Dependencies

The project uses:

Requests

HTTP client used for communicating with the target.

Colorama

Provides reliable colored terminal output on Windows.

Install all dependencies with:

pip install -r requirements.txt

Responsible Disclosure

If you discover a vulnerable installation that you are authorized to assess:

Confirm the affected version.
Notify the system owner or responsible security team.
Recommend updating to a fixed version.
Avoid unnecessary exploitation.
Preserve relevant evidence without accessing unrelated data.

Do not use this tool to scan systems without authorization.

Disclaimer

This project is provided for defensive security research, vulnerability assessment, education, and authorized penetration testing.

Most Popular

CVE-2026-14281-check