# WordPress Vulnerability Watch (`kayorama/wp-vulnerability-watch`) Actor

Monitor WordPress plugins, themes, and core for known vulnerabilities using the public WPVulnerability database.

- **URL**: https://apify.com/kayorama/wp-vulnerability-watch.md
- **Developed by:** [Kayorama](https://apify.com/kayorama) (community)
- **Categories:** Developer tools, SEO tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 wordpress component vulnerability checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## WordPress Vulnerability Watch

Monitor WordPress plugins, themes, and core for known vulnerabilities using the public [WPVulnerability](https://www.wpvulnerability.com/) database.

The Actor is built for recurring security watch workflows:

- checks WordPress.org plugins and themes by slug;
- optionally checks a specific WordPress core version;
- matches known vulnerabilities against the installed version when supplied;
- reports severity, CVSS score, fixed-in version, affected status, and source advisories;
- preserves isolated baselines so repeat runs show `new`, `existing`, and `resolved` findings;
- charges one `component-vulnerability-check` event per attempted plugin, theme, or core check in pay-per-event mode.

### What this Actor does not do

- It does not require WordPress admin credentials.
- It does not scan private files, databases, users, or server configuration.
- It does not prove exploitability on a specific site.
- It is not a guarantee that a site is safe, patched, or compliant.

Use the output as a prioritized public-vulnerability watch, then confirm remediation with vendor guidance, backups, and a staging test.

### Input

```json
{
  "plugins": [
    { "slug": "woocommerce", "installedVersion": "10.0.0" },
    { "slug": "wordfence", "installedVersion": "8.1.0" }
  ],
  "themes": [
    { "slug": "flavor", "installedVersion": "1.2.0" }
  ],
  "coreVersion": "6.8.1",
  "minimumSeverity": "medium"
}
```

If `installedVersion` is omitted for a plugin or theme, the Actor looks up the current WordPress.org directory version and uses it for affected-version matching.

### Output

Dataset rows include:

- `component_snapshot` — per-component totals, highest severity, and affected finding IDs;
- `vulnerability_finding` — public advisory evidence, CVSS data, affected status, fixed-in version, and change state;
- `component_fetch_error` — failed public API lookups;
- `summary` — requested, processed, findings, new/resolved findings, and spending-limit state.

The key-value store also contains `OUTPUT` and `SUMMARY`.

### Recurring state

By default, successful complete runs update a named Apify key-value store so the next run can distinguish:

- `new` — not affected in the previous stored baseline;
- `existing` — still affected;
- `resolved` — previously affected but no longer matching the monitored version or public dataset.

Set `useStoredState: false` for one-off checks.

### Data source

Public vulnerability data comes from the WPVulnerability API, which is open and does not require an API key for normal plugin, theme, core, and infrastructure endpoints. The Actor also uses the public WordPress.org directory API when it needs the current plugin or theme version.

# Actor input Schema

## `plugins` (type: `array`):

WordPress.org plugins with optional installed versions. If omitted, the current directory version is used.

## `themes` (type: `array`):

WordPress.org themes with optional installed versions.

## `coreVersion` (type: `string`):

Optional WordPress core version to check, such as 6.8.1.

## `minimumSeverity` (type: `string`):

Only report vulnerabilities at or above this CVSS severity.

## `previousSnapshots` (type: `array`):

Optional prior component\_snapshot records. Explicit input, including an empty list, takes precedence over stored state.

## `useStoredState` (type: `boolean`):

Compare with and safely update prior component snapshots in a named key-value store after a complete run.

## `stateStoreName` (type: `string`):

Named Apify key-value store used to preserve component baselines across separate runs.

## `stateRecordKey` (type: `string`):

Optional explicit record key for isolating one monitoring set within the named state store.

## Actor input object example

```json
{
  "plugins": [
    {
      "slug": "woocommerce",
      "installedVersion": "10.0.0"
    }
  ],
  "themes": [],
  "minimumSeverity": "low",
  "useStoredState": true,
  "stateStoreName": "wp-vulnerability-watch-state"
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("kayorama/wp-vulnerability-watch").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("kayorama/wp-vulnerability-watch").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call kayorama/wp-vulnerability-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=kayorama/wp-vulnerability-watch",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/8awD7fObGJ84DT2Uy/builds/kIL4SC6AdUkc5KZAm/openapi.json