Skip to content
Web

CVE-2026-74803

10.0
Critical
EPSS 0.31%Patch availableAug 19, 2026

Unauthenticated arbitrary file upload in YOOtheme 'Zoo' Joomla extension allowing attackers to upload malicious files.

common questions

Is CVE-2026-74803 being exploited?

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

How severe is CVE-2026-74803?

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

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

What does CVE-2026-74803 affect?

CVE-2026-74803 affects YOOtheme Zoo Joomla extension < 4.1.64, Joomla sites using YOOtheme Zoo. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74803?

Upgrade Zoo to >=4.1.64; remove shells, audit uploads, apply WAF rules

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

executive summary
technical analysis
affected
YOOtheme Zoo Joomla extension < 4.1.64Joomla sites using YOOtheme Zoo
impact

Unauthenticated arbitrary file upload that can be used to upload web shells -> remote code execution, site compromise, data theft, malware hosting.

action required

Immediate action required

affected versions
yootheme.com Zoo extension for Joomla
  • affected1.0.0-4.1.63

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