Skip to content
Web

CVE-2026-39776

8.0
High
EPSS 0.38%Oct 6, 2026

Editor RCE in Tabs WordPress plugin (<=2.5)

common questions

Is CVE-2026-39776 being exploited?

Not confirmed. CVE-2026-39776 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-39776?

CVE-2026-39776 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-39776?

Not known from our data. No patch reference has been recorded for CVE-2026-39776, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-39776 affect?

CVE-2026-39776 affects Tabs (WordPress plugin) <=2.5, WordPress sites using Tabs/tabs-responsive plugin. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-39776?

Remove/disable plugin or isolate sites and apply vendor patch when released; restrict editor privileges.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Tabs (WordPress plugin) <=2.5WordPress sites using Tabs/tabs-responsive plugin
impact

An attacker with editor access can execute arbitrary code as the webserver (PHP/commands), deploy web shells, deface sites, and pivot to internal assets.

action required

Immediate action required

affected versions
wpshopmart Tabs
  • affected<= 2.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free