Skip to content
Web

CVE-2026-58480

9.2
Critical
EPSS 4%Patch availableJul 8, 2026

Unauthenticated RCE via arbitrary file upload in Blocksy Companion Pro plugin.

common questions

Is CVE-2026-58480 being exploited?

Not confirmed. CVE-2026-58480 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 3.6% probability of exploitation in the next 30 days.

How severe is CVE-2026-58480?

CVE-2026-58480 is rated Critical with a CVSS score of 9.2. 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-58480?

Yes. A fix has been recorded for CVE-2026-58480. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-58480 affect?

CVE-2026-58480 affects Blocksy Companion Pro < 2.1.47, WordPress sites using Blocksy theme/plugin, Web servers executing uploaded PHP. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-58480?

Update to Blocksy Companion Pro >=2.1.47; remove suspicious uploads; restrict PHP execution in uploads

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

executive summary
technical analysis
affected
Blocksy Companion Pro < 2.1.47WordPress sites using Blocksy theme/pluginWeb servers executing uploaded PHP
impact

Unauthenticated remote code execution: attackers can upload double-extension PHP files (e.g., shell.woff2.php) via Advanced Reviews/Custom Fonts to execute arbitrary code.

action required

Immediate action required

affected versions
Creative Themes Blocksy Companion
  • affected<= 2.1.46
vendor says fixed in2.1.47

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