Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-74253 – Unauthenticated Remote Code Execution – Sourcerer extension for Joomla (versions 1.

Be the first to know when new zero-days emerge:

Summary

CVE-2026-74253 is a critical, unauthenticated remote code execution vulnerability in the Sourcerer extension for Joomla, developed by Regular Labs. The flaw stems from improper control of code generation (CWE-94): Sourcerer processes {source} blocks found anywhere in Joomla’s final rendered HTML output without reliably verifying where that code actually originated, allowing an attacker to smuggle in and execute arbitrary code without any authentication. The vulnerability carries the maximum CVSS score of 10.0 and affects all Sourcerer versions from 1.0.0 through 13.1.1.

Technical details

  • Root cause: Sourcerer scans Joomla’s fully rendered HTML for {source} tags and executes the embedded code (including PHP), but it does not reliably distinguish between code that was legitimately authored/verified within trusted content (e.g., articles created by Super Users) and code that was reflected or injected into the page output through other means (e.g., search results, AJAX responses, module output, or other unverified rendering paths).
  • Trigger conditions: Any mechanism that causes attacker-controlled input containing a {source} block to appear in the site’s final rendered HTML can cause Sourcerer to treat it as legitimate embedded code and execute it.
  • Attack vector: Network — the vulnerability can be exploited remotely, requires no privileges, and requires no user interaction.
  • Impact: Full compromise of confidentiality, integrity, and availability of the affected Joomla site, since arbitrary PHP/code execution on the web server is possible without authentication.

Affected software

  • Sourcerer extension for Joomla (developed by Regular Labs), versions 1.0.0 through 13.1.1

Severity

  • CVSS Score: 10.0 (Critical)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
  • Weakness: CWE-94 (Improper Control of Generation of Code) / CAPEC-242 (Code Injection)

Mitigation and recommended actions

  • Immediate: Upgrade Sourcerer to version 14.0.0 or later, which contains the vendor-designated security fix that "prevents reflected or otherwise unverified rendered Sourcerer code from executing by default while preserving verified article and Custom module code."
  • Note that the 14.0.0 update introduces backward-compatibility breaks: previously trusted Sourcerer output generated only during component, module, head, or final rendering may be removed by default, and Pro sites must explicitly opt in to allow unverified CSS, JavaScript, or PHP code. Administrators should review Sourcerer security settings after upgrading to confirm intended behavior is preserved.
  • If immediate patching is not possible: Restrict or disable Sourcerer in any component, module, or content area accessible to non-trusted or non-backend users, and audit existing site content for injected {source} blocks in areas that accept user-submitted or reflected input.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge