dbcve.org
SourcererApplication · Regularlabs

CVE-2025-22204

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-04
Fix available
A fix is available. Upgrade to 11.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper control of generation of code in the sourcerer extension for Joomla in versions before 11.0.0 lead to a remote code execution vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The sourcerer extension for Joomla versions prior to 11.0.0 contains an improper control of code generation vulnerability that allows remote attackers to execute arbitrary code on the affected system. This is a critical code injection flaw in a widely-used Joomla extension that enables complete system compromise.

MitigationUpgrade the sourcerer extension to version 11.0.0 or later immediately, as no workarounds are available for this RCE vulnerability. Since this is a third-party extension, ensure the upgrade is compatible with the Joomla version in use and test thoroughly after deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SourcererApplication
Affected:< 11.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Regularlabs Sourcerer extension in Joomla
    Log into the Joomla Administrator panel and navigate to System > Manage > Extensions. Search for 'Sourcerer' in the name field to confirm the extension is installed on your system.
    Affected if The extension named 'Sourcerer' or 'Regularlabs - Sourcerer' appears in the extensions list.
  2. Identify the installed version number
    In the Extensions manager, locate the Sourcerer extension and examine the version column. If the version column is not displayed, click on the extension name to view its details page where the version is typically shown.
    Affected if You can retrieve a version number from the extension details.
  3. Compare against vulnerable version range
    Take the version number you found and compare it to the affected range: any version prior to 11.0.0. This includes versions such as 10.x, 9.x, 8.x, and earlier major versions.
    Affected if The installed version is less than 11.0.0 (for example: 10.5.3, 9.1.2, 8.0.1).
  4. Verify extension is enabled
    In the Extensions manager, check the Status column for the Sourcerer extension. A green checkmark or 'Enabled' status indicates the extension is active.
    Affected if The extension is installed, vulnerable (version < 11.0.0), and currently enabled.

Your environment is affected if the Regularlabs Sourcerer extension is installed, enabled, and running any version prior to 11.0.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.0.0 or later
Fixed in 11.0.0
Interim mitigation

Upgrade the sourcerer extension to version 11.0.0 or later immediately, as no workarounds are available for this RCE vulnerability. Since this is a third-party extension, ensure the upgrade is compatible with the Joomla version in use and test thoroughly after deployment.

Recommended fix High confidence

11.0.0

  1. 1. Backup your Joomla site and database before making any changes
  2. 2. Navigate to the Joomla Administrator panel
  3. 3. Go to Extensions > Manage > Install
  4. 4. Download the Sourcerer version 11.0.0 from the official source (regularlabs.com)
  5. 5. Upload and install the new version through Joomla's extension manager
  6. 6. After installation, verify the installed version shows 11.0.0 in Extensions > Manage > Extensions
  7. 7. Test that the Sourcerer functionality works correctly on your site
Caveat Review the regularlabs.com changelog for any breaking changes between your current version and 11.0.0 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sourcerer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22204 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data