PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-66494 joomshaper.com CVE debrief

CVE-2026-66494: Unauthenticated stored XSS in Joomla Extension SP Page Builder < 6.7.0. The vulnerability allows an unauthenticated attacker to store malicious JavaScript in a Joomla site's database via a single HTTP request, which executes when an administrator opens the SP Page Builder editor. This issue has a CVSS score of 8.7 and is considered HIGH severity. Affected systems require immediate attention to prevent potential XSS attacks. Review compensating controls for exposed systems while remediation is scheduled and verified. Check relevant monitoring, detection, and logs for exposed assets that need extra review. Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Vendor
joomshaper.com
Product
SP Page Builder extension for Joomla
CVSS
HIGH 8.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-07
Original CVE updated
2026-08-26
Advisory published
2026-08-07
Advisory updated
2026-08-26

Who should care

Administrators of Joomla sites using SP Page Builder, security teams monitoring for XSS vulnerabilities, and operators of Joomla sites that use SP Page Builder for content creation should be aware of this vulnerability. They should prioritize updating to version 6.7.0 or later to prevent potential XSS attacks. Additionally, security teams should monitor for suspicious activity on Joomla sites using SP Page Builder and implement additional security measures to prevent XSS attacks. This vulnerability has a CVSS score of 8.7 and is considered HIGH severity, indicating a high level of risk to affected systems. Reviewing compensating controls for exposed systems while remediation is scheduled and verified is also recommended. Checking relevant monitoring, detection, and logs for exposed assets that need extra review is crucial. Tracking exceptions, retesting remediated assets, and closing the item only after evidence is documented are also essential steps. The CVE record and the NIST NVD detail page provide further information on this vulnerability. Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up. Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Implementing additional security measures to prevent XSS attacks is also recommended. Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Asset inventory management and source tracking are also recommended to ensure that all affected systems are accounted for and that the vulnerability is properly managed. Rollback/change windows should be considered to minimize downtime during remediation. Monitoring for suspicious activity on Joomla sites using SP Page Builder is crucial to detect potential attacks. Compensating controls, such as web application firewalls, can be implemented to prevent exploitation of this vulnerability. Security teams should also review their incident response plans to ensure they are prepared to respond to potential attacks. Overall, a comprehensive approach that includes updating to version 6.7.0 or later, monitoring for suspicious,

Technical summary

The CVE record describes an unauthenticated stored XSS vulnerability in the Shapes API endpoint of SP Page Builder versions less than 6.7.0. An attacker can store malicious JavaScript in a Joomla site's database via a single HTTP request, which executes when an administrator opens the SP Page Builder editor. This vulnerability has a CVSS score of 8.7 and is considered HIGH severity. The vulnerability affects Joomla sites using SP Page Builder versions less than 6.7.0. Administrators of Joomla sites using SP Page Builder should prioritize updating to version 6.7.0 or later to prevent potential XSS attacks.

Defensive priority

Administrators of Joomla sites using SP Page Builder should prioritize updating to version 6.7.0 or later to prevent potential XSS attacks.

Recommended defensive actions

  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Implement additional security measures to prevent XSS attacks

Evidence notes

The CVE record indicates an unauthenticated stored XSS vulnerability in the Shapes API endpoint of SP Page Builder versions less than 6.7.0. An attacker can store malicious JavaScript in a Joomla site's database via a single HTTP request, which executes when an administrator opens the SP Page Builder editor. The vulnerability has a CVSS score of 8.7 and is considered HIGH severity. Administrators of Joomla sites using SP Page Builder should prioritize updating to version 6.7.0 or later to prevent potential XSS attacks. Evidence of this vulnerability is limited to the CVE record and the NIST NVD detail page.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-66494 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-66494

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-66494 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66494

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.