Run wpscan --url https://example.com -e vp --api-token YOUR_TOKEN to enumerate WordPress plugins with known vulnerability records, or replace vp with vt to check themes. WPScan can identify installed components without a token, but it needs a WPScan API token to show associated vulnerability data. Use it only on a site you own or are explicitly authorized to test, then verify every finding, remediate it, and rescan.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What WPScan finds—and what a finding means
WPScan is a black-box WordPress security scanner for security professionals, site owners and blog maintainers. Black-box means it examines the site from the outside rather than reading its server filesystem or application source. It can identify the WordPress version, installed plugins and themes, usernames, exposed backups and database exports, and other WordPress-specific exposure points.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Its vulnerability information comes from the WPScan WordPress Vulnerability Database API. The API supports lookups for WordPress core, plugin and theme vulnerabilities by component slug and version. WPScan says many records are manually verified and that it is a CVE Numbering Authority for WordPress core, plugin and theme vulnerabilities. That makes the database useful for matching a detected version to an affected-version range, but the match is still an investigation lead.
A vulnerability record does not prove that an attacker successfully exploited your particular installation. Exploitability can depend on configuration, enabled features, authentication and other deployment details. Treat the result as a reason to verify the component and its exposure, not as evidence of a completed compromise.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Authorization and prerequisites
Scan only websites you own or have written permission to assess. A production scan can generate requests, reveal component information and trigger monitoring or rate limits. If you are testing for a client, keep the authorization, scope, permitted dates and emergency contact with the scan notes.
- A reachable WordPress site URL, such as
https://example.com. - WPScan installed in an environment where you can run its command-line interface, or access to the current WPScan WordPress workflow.
- A WPScan API token when you want vulnerability records rather than component identification alone.
- Permission to review and change the target site if the scan finds an outdated component.
Register with WPScan to obtain an API token. Store the token as a secret: do not paste it into public tickets, shell history that is shared with other users, screenshots or source control.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteRun a baseline scan
Start with the documented URL-only command:
wpscan --url https://example.comThis baseline can identify WordPress and discover components, but vulnerability records are not displayed unless the request includes a token. A baseline is useful for confirming that the target is reachable and for seeing what WPScan can detect before you change enumeration depth.
To include vulnerability data, add the token:
wpscan --url https://example.com --api-token YOUR_TOKENReplace both values with the authorized site and your token. Keep the output with the scan date, target, WPScan version and command options so that a later scan can be compared with the original.
Find vulnerable plugins
Use the vulnerable-plugin enumeration code vp:
wpscan --url https://example.com -e vp --api-token YOUR_TOKENThe command asks WPScan to discover plugins and associate detected versions with records in the vulnerability database. For each result, record the exact plugin slug and version as reported. The slug is important because database lookups are component-specific; a display name alone can be ambiguous.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Choose a plugin detection mode
Plugin discovery and vulnerability matching are related but distinct. The scanner first has to discover a plugin and its version, then the API can check that version. WPScan documentation says plugin enumeration defaults to passive detection. Passive mode makes fewer requests and is gentler on the target, but it can return fewer results. When broader discovery is needed, the documentation recommends changing the mode to mixed.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Approach | What it prioritizes | When to use it | Trade-off |
|---|---|---|---|
| Passive detection | Lower request volume | Routine checks, rate-sensitive sites and an initial inventory | Some plugins may not be discovered |
| Mixed detection | Broader discovery | A follow-up when passive results look incomplete or you need more coverage | More requests and greater load than passive detection |
| Aggressive detection, where supported by the installed CLI | Coverage over request economy | Controlled assessments with explicit permission and a request budget | Use the help for your installed version and expect higher request activity |
Do not silently assume that a short passive result is a complete inventory. If your authorization and operational limits permit it, use mixed detection for the broader pass and note the mode in your report. The exact option syntax is version-dependent, so check the help output of the WPScan version you are running rather than copying an old example unchanged.
Find vulnerable themes
Use the vulnerable-theme enumeration code vt:
wpscan --url https://example.com -e vt --api-token YOUR_TOKENAs with plugins, preserve the detected theme slug and version. A site can contain more than one installed theme, and a theme that is not currently active can still matter if it remains on the server and is vulnerable. Whether an unauthenticated scan can see every inactive component depends on what the site exposes; the authenticated workflow described below is intended to provide an authoritative active and inactive list.
Use WPScan 4.0’s authenticated component workflow
WPScan 4.0 documentation adds an explicit vulnerable-component workflow that uses a WordPress Application Password and queries the WordPress REST API. It is designed to obtain the authoritative list of every active or inactive plugin and theme, then check those components against vulnerability data.
This authenticated approach addresses a visibility problem: an external scan may not be able to identify components that leave no public traces, while an authenticated REST request can ask WordPress for its installed component list. Treat the Application Password as a credential with access to the account that created it. Use a dedicated account where your site’s access policy allows one, limit privileges to what the documented workflow requires, and revoke the password when the assessment is finished or the engagement ends.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
- Create a WordPress Application Password for the authorized assessment account using your site’s WordPress account settings.
- Run the current WPScan 4.0 authenticated vulnerable-component workflow as documented for your installed release, supplying the site URL and Application Password securely.
- Confirm that the WordPress REST API is reachable from the scanning environment; the workflow depends on querying it directly.
- Review the returned active and inactive plugin and theme list, then match each reported version to its vulnerability record.
- Remove the credential from scripts, logs and temporary files after the scan, and revoke it if it is no longer needed.
Older command-line examples that only change --plugins-detection describe CLI discovery behavior. They should not be presented as a substitute for the current authenticated REST workflow when the goal is a complete active/inactive inventory.
Understand API requests and the free limit
The WordPress.org listing for the WPScan plugin documents 25 API requests per day on the free plan. It also describes the request model: one request for the WordPress version, one request for each installed plugin and one request for each installed theme. The allowance is therefore consumed by the size of the inventory, not just by the number of times you start a scan.
For planning, the same listing reports an average of 22 installed plugins per WordPress website. A site with that many plugins plus several themes can approach or exceed a 25-request daily allowance, depending on the exact inventory. Count the components before scheduling repeated scans, and avoid spending the daily allowance on unnecessary duplicate runs.
| Scan situation | Token needed for vulnerability records? | What consumes API requests? |
|---|---|---|
| URL-only discovery | No; component identification can still work | No associated vulnerability records are displayed without the token |
| Token-based scan | Yes | WordPress version plus each detected plugin and theme, according to the documented model |
| Authenticated active/inactive inventory | Yes for vulnerability matching | The authoritative component list and its vulnerability lookups, subject to the plan’s allowance |
If you need more capacity than the free plan provides, check the current WPScan plan terms before changing your schedule. Do not assume that a paid allowance, price or partner offer remains unchanged.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsInterpret a result without overclaiming
For every finding, capture these fields in a remediation record:
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Target URL and scan date.
- Component type: WordPress core, plugin or theme.
- Exact slug and detected version.
- Vulnerability identifier or database record reference shown by WPScan.
- Affected-version range and fixed version, as stated in the vulnerability record.
- Whether the component is active or inactive, if the authenticated workflow reports that status.
- Operational owner, planned action and completion date.
Then follow this sequence:
- Open the vulnerability record and read the affected-version range rather than relying on the component name alone.
- Confirm the vendor’s fixed release from the component’s official update channel.
- Update to the fixed release, or remove the component if it is unnecessary or no supported fix exists.
- When severity or exposure warrants it, review web-server, WordPress and security-monitoring logs for indicators associated with the affected component.
- Run WPScan again and verify that the detected version and vulnerability status have changed.
A result that disappears after an update is evidence that the version match changed; it is not proof that an earlier compromise did or did not occur. Log review and incident-response decisions are separate from the scanner’s discovery function.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Unauthenticated and authenticated scans: which should you choose?
| Decision axis | Unauthenticated scan | Authenticated REST workflow |
|---|---|---|
| Setup | Needs a target URL; a token is added for vulnerability data | Needs a WordPress Application Password and REST API access |
| Visibility | Sees what the public site exposes | Queries the authoritative list of active and inactive plugins and themes |
| Best use | External exposure checks, quick baselines and assessments where credentials cannot be used | Owner-operated inventory and checks where inactive components must be included |
| Risk to manage | Public requests can be logged or rate-limited | Credential handling and REST API access must be controlled |
These approaches are complementary. Start externally when you need to understand public exposure, then use authenticated access when you are responsible for the site and need a complete installed-component list.
Use scheduled scans and notifications carefully
The WordPress.org listing describes scheduled daily scans and email notifications, along with checks for exposed debug logs, backup wp-config.php files, XML-RPC exposure, repository files, default secret keys, exported databases, weak passwords and HTTPS status. Those checks extend beyond plugin and theme version matching, so decide which alerts belong in your site’s normal maintenance process.
A daily schedule is useful only if it fits the API allowance and someone owns the response. Set an alert recipient who can update a component, investigate logs or escalate an incident. If a site has many components, calculate the documented per-component request model before enabling frequent scans.
Troubleshoot common outcomes
The scan lists components but no vulnerabilities
Check whether --api-token YOUR_TOKEN was included and whether the token is valid. WPScan can enumerate and identify components without a token, but associated vulnerability records are omitted in that mode.
Plugin results look incomplete
Passive detection is the default and intentionally makes fewer requests. If your authorization permits additional traffic, repeat the discovery using the documented mixed mode and compare the component lists. For a definitive active/inactive inventory, use the WPScan 4.0 authenticated REST workflow.
The daily allowance is exhausted
Review how many plugins and themes were checked, remembering that the documented model includes a request for the WordPress version and one for every installed plugin and theme. Stop duplicate scans for the day, record the partial result, and schedule the next run after the allowance resets or use an account plan with suitable capacity.
Recommended Free Tools
The REST workflow cannot return the component list
Verify the Application Password, account authorization and REST API reachability. A blocked or unavailable REST endpoint prevents the authenticated workflow from retrieving its authoritative list; resolve that access issue within the site’s security policy before treating the inventory as complete.
A vulnerability is reported after an update
Check the exact detected version, slug and affected-version range. Confirm that the update actually reached the target environment and that the fixed release is the one named by the vendor. Then rescan. If the same vulnerable version is still detected, investigate deployment, caching or update failures rather than dismissing the result.
A repeatable operating procedure
- Define the authorized target, timing and request limits.
- Run
wpscan --url https://example.comto establish reachability and a baseline. - Add the API token for vulnerability records.
- Run
-e vpfor vulnerable plugins and-e vtfor vulnerable themes. - Use mixed detection when passive discovery is insufficient and the extra request load is approved.
- For an owner-operated assessment, use WPScan 4.0’s Application Password and REST workflow to include active and inactive components.
- Record slugs, versions, affected ranges and fixed releases.
- Update or remove affected components, then review logs when severity warrants it.
- Rescan and retain both the original and verification outputs.
Command reference
| Purpose | Command |
|---|---|
| Baseline scan | wpscan --url https://example.com |
| Scan with vulnerability data | wpscan --url https://example.com --api-token YOUR_TOKEN |
| Enumerate vulnerable plugins | wpscan --url https://example.com -e vp --api-token YOUR_TOKEN |
| Enumerate vulnerable themes | wpscan --url https://example.com -e vt --api-token YOUR_TOKEN |
The practical rule is simple: use the token when you need vulnerability matches, choose a detection mode that fits the target’s request tolerance, use authenticated REST access when inactive components must be authoritative, and verify remediation with a new scan.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
