Skip to main content
Menu
CVEs

Staggs remote code execution in WordPress plugin

CVE-2026-78287EUVD-2026-123356GHSA-FRHH-FMQ4-P6RWPublished November 11, 2026, updated Needs attention

10.0CriticalCNA
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in 3.4.0
Who is exposed
Not reported

Summary

The STAGGS plugin for WordPress, made by Staggs, has a code injection flaw that allows remote code inclusion. An attacker can reach it over the network without logging in and run their own code on the affected site.

Written by a model

Original description

Improper Control of Generation of Code ('Code Injection') vulnerability in Staggs STAGGS staggs allows Remote Code Inclusion.This issue affects STAGGS: from n/a through 3.3.0.

Who should check

Teams running the WordPress STAGGS plugin version 3.3.0 or earlier on WordPress sites.

“WordPress STAGGS Plugin <= 3.3.0 is vulnerable to a high priority Remote Code Execution (RCE)”

patchstack.com

What to do

Upgrade to a fixed version: 3.4.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-78287 (WordPress STAGGS plugin <= 3.3.0 - Remote Code Execution (RCE) vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-78287 (entry last updated 2026-11-12):
Affected:
- Staggs STAGGS: fixed in 3.4.0
Fixed versions: 3.4.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-78287 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-78287 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/staggs/vulnerability/wordpress-staggs-plugin-3-3-0-remote-code-execution-rce-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-78287
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-78287"}.

Affected versions

cve.now Index

52of 100 · methodology v3
  • Exploitation22/40Public exploit on Exploit-DB or GitHub
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 10.0, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 57 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

    1 day
  5. Record last updated5 days
  6. Exploit code on GitHub

    0xTerror/CVE-2026-78287

Public exploit activity

20Posted on X by cve.now100%0Nov 11Nov 22
  • GitHub PoC repos: 2
  • EPSS: 0.58%
  • Posted on X by cve.now Nov 11

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 1

Evidence 5

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-78287
RecordNVD · CVE-2026-78287
Public exploit code 2Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · 0xTerror/CVE-2026-78287 · Repository
ExploitGitHub · evenomn/CVE-2026-78287 · Repository
Other links 1
Linkpatchstack.com · database/wordpress/plugin/staggs/vulnerability/wordpress-staggs-plugin-3-3-0-remote-code-execution-rce-vulnerability?_s_id=cve

Questions about CVE-2026-78287

Is CVE-2026-78287 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: cve.now feed data

What does this mean?

The plugin has a flaw that lets an attacker run any command on the server the site runs on, from anywhere in the world.

Source: patchstack.com

Which versions are affected by CVE-2026-78287?

staggs: through 3.3.0 (fixed in 3.4.0).

Source: cve.now feed data

Am I affected, and how do I check?

STAGGS by Staggs, a WordPress plugin, in all versions up to and including 3.3.0. To check, look at the plugin version shown in the WordPress admin Plugins screen.

Source: patchstack.com

How do I fix CVE-2026-78287?

Update STAGGS to version 3.4.0 or later, which the advisory says resolves the vulnerability.

Source: patchstack.com

No corrections so far. Something wrong on this page? Report an error.