CVE
WordPress STAGGS plugin <= 3.3.0 - Remote Code Execution (RCE) vulnerability
The WordPress STAGGS plugin, version 3.3.0 and earlier, lets an attacker run any command on the server. Fixed in 3.4.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.4.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.4.0.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the 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 their WordPress sites.
Read the source excerpt
“WordPress STAGGS Plugin <= 3.3.0 is vulnerable to a high priority Remote Code Execution (RCE)”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
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-11):
Affected:
- Staggs STAGGS: through 3.3.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
- https://www.cve.org/CVERecord?id=CVE-2026-78287
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"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- staggs
through 3.3.0
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw lets an attacker run any command on the server that hosts the site. This is remote code execution, meaning the attacker does not need to be logged in on the server itself.Source: patchstack.com, cve.org
Which versions are affected by CVE-2026-78287?
staggs: through 3.3.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions of the STAGGS plugin up to and including 3.3.0 are affected, with no known lower bound. To check, look at the plugin version shown in the WordPress admin Plugins page.Source: patchstack.com, cve.org
How do I fix CVE-2026-78287?
Update the STAGGS plugin to version 3.4.0 or later, the first version listed as fixed.Source: patchstack.com, cve.org