Skip to content
Web

CVE-2026-60028

8.6
High
EPSS 0.42%Jul 21, 2026

Authenticated stored XSS in Quix Page Builder Pro allows persistent script injection executed by visitors/admins.

common questions

Is CVE-2026-60028 being exploited?

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

How severe is CVE-2026-60028?

CVE-2026-60028 is rated High with a CVSS score of 8.6. 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-60028?

Not known from our data. No patch reference has been recorded for CVE-2026-60028, 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-60028 affect?

CVE-2026-60028 affects Joomla CMS with Quix Page Builder Pro extension. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60028?

Apply vendor patch; if unavailable disable/remove extension and audit/reset admin sessions.

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

executive summary
technical analysis
affected
Joomla CMS with Quix Page Builder Pro extension
impact

Authenticated builder users can inject persistent JavaScript, enabling account takeover, session hijacking, admin compromise, or malware delivery.

action required

Patch when possible

affected versions
themexpert.com Quix Page Builder Pro extension for Joomla
  • affected1.0-6.2.0

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