On this page
Start with a result you can check
Your first scan should leave you with a short list of findings you understand, each tied to evidence and a next step. A report full of coloured badges is only the beginning. Keep a notebook with the tool version, command, date, target and the evidence behind each finding.
The WPSecScan download page currently documents a Windows executable and a Python installation. It also documents a demo mode. This walkthrough starts there so you can learn the report before sending requests to a real site.
Install from the documented distribution
Open the download page and choose the distribution for your system. For a downloaded release, follow the release-verification instructions before execution. Record the release tag and the verification result with your notes.
For Python, the documented installation command is:
pip install wpsecscan
Use a dedicated Python environment for this exercise. The download page specifies Python 3.10 or later. Package installation and verification of a downloaded executable are different workflows; do not treat an executable's checksum as verification of a package installed from a registry. Installation source
To repeat the recorded package version, run these commands in a new working directory. They use the environment's executable directly, so activation is unnecessary. Python must already be installed; Linux installations may require their distribution's venv package. Python virtual-environment documentation
On Windows, in PowerShell:
py -m venv .venv
.\.venv\Scripts\python.exe -m pip install wpsecscan==2.9.1
.\.venv\Scripts\wpsecscan.exe --demo --no-live --no-color
On Linux or macOS:
python3 -m venv .venv
.venv/bin/python -m pip install wpsecscan==2.9.1
.venv/bin/wpsecscan --demo --no-live --no-color
The Linux demo was run for this article. The Windows commands follow Python's documented environment layout but were not executed in this review. Pinning WPSecScan selects the demonstrated release; it does not pin every dependency or make different operating systems byte-for-byte identical.
Read the demo before choosing a target
The documented demo command is:
wpsecscan --demo
Treat its findings as examples, not observations about your website. Save the complete output, including errors, and record the command's exit code. If your installed version rejects the command, stop and compare its version with the download instructions. Demo instructions

A recorded demo result
On 17 October 2026, an isolated Linux run of the pinned WPSecScan 2.9.1 package completed with exit code 0 using:
wpsecscan --demo --no-live --no-color
The saved JSON contained 25 check records and 28 synthetic findings. The chart uses those recorded counts; it is not a screenshot or a scan of a real website. The demo target was https://wpsecscan-demo.invalid.
| Demo severity | Recorded findings |
|---|---|
| Critical | 6 |
| High | 4 |
| Medium | 8 |
| Low | 4 |
| Informational | 6 |
Those labels and counts describe the tool's sample data only. Do not copy its sample CVE identifiers into a real vulnerability investigation. For each finding in your own later report, fill in these fields:
| Field | What to record |
|---|---|
| Observation | The exact item reported by the tool |
| Evidence | The URL, response or version information supplied |
| Applicability | Whether you can reproduce the observation on your installation |
| Next action | A specific investigation or proposed change, with an owner |
Do not turn a missing security header into an assumed compromise, or an empty report into a clean bill of health. Those would be interpretations requiring additional evidence.
Move to an authorised site deliberately
Agree the target, scan options and timing with the person responsible for the site. Read the current command help and check what requests the selected mode sends. Running a scanner on your own computer does not by itself give that scanner access to a remote server's files.
For the first real run, keep the same notebook and separate confirmed observations from items awaiting investigation. Reproduce a finding before proposing a fix; after an approved change, repeat the relevant check and retain both results. Your useful deliverable is that evidence trail, not a particular badge count.




