Skip to main content
mySites.guru
New this monthChecklistsCoreFilestmp Folder ScanDirectAdmin ImportcPanel Quick AddDatabase ChecksStaff Offboarding
CVE-2026-102802HighCVSS 8.9CVE published 2 November 2026Added to mySites.guru 2 November 2026

Sourcerer (sourcerer) 13.0.0 to below 17.0.1 - Authenticated PHP Execution via Articles Anywhere Included Articles

CVE-2026-102802 (published 2 Nov 2026, CVSS 4.0 8.9 High). When Sourcerer is used together with Articles Anywhere, an article included through an Articles Anywhere tag could have its Sourcerer PHP run under the trust of the HOST article rather than its own author, so a content author whose own articles are not trusted to run Sourcerer PHP could get their PHP executed by having their article pulled into a trusted article. It needs a logged-in user who can create or edit articles; nothing unauthenticated. Sites that do not have Articles Anywhere installed are not exposed to this issue, but this rule cannot check for that, so it flags every Sourcerer install in the affected range. The fix is joint: update Sourcerer to 17.0.1 or later AND Articles Anywhere to 20.1.1 or later (31 Oct 2026). Free and Pro editions are both affected. Temporary mitigation: restrict which user groups can create or edit articles, or disable Sourcerer PHP in articles until both are updated.

Is my site affected?

CVE-2026-102802 is checked by 2 rules. Find the extension and release line your site runs:

ExtensionAffected versionsFixed inWhat to do
Sourcererfrom 13.0.0 up to but not including 17.0.117.0.1Update Sourcerer to 17.0.1 or later.
Articles Anywherefrom 19.0.0 up to but not including 20.1.120.1.1Update Articles Anywhere to 20.1.1 or later.

How CVE-2026-102802 is scored

The base metrics as Joomla CNA published them, and what each one means for a site running an affected version. Threat and environmental metrics are left out: they describe a moment or a particular install rather than the flaw.

8.9 High

CVSS 4.0, scored by Joomla CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

How it is reached

AV:N Attack vector
Network. Reachable across the internet
AC:L Attack complexity
Low. Nothing to work around, it just works
AT:P Attack requirements
Present. Needs a particular deployment or race to line up
PR:H Privileges required
High. Needs an account with elevated rights
UI:N User interaction
None. Nobody has to be tricked into anything

What it does to the site

VC:H Confidentiality
High. Everything the site holds can be read
VI:H Integrity
High. Data and files can be altered at will
VA:H Availability
High. The site can be taken down

What it does beyond the site

SC:H Confidentiality
High. Data on other systems can be read
SI:H Integrity
High. Other systems can be altered
SA:H Availability
High. Other systems can be taken down

Timeline

  1. 31 October 2026mySites.guru check added for Articles Anywhere (from 19.0.0 up to but not including 20.1.1)
  2. 31 October 2026We published: Articles Anywhere 20.1.1 and Sourcerer 17.0.1 Fix One Issue Together
  3. 2 November 2026CVE-2026-102802 record published by its CNA
  4. 2 November 2026mySites.guru check added for Sourcerer (from 13.0.0 up to but not including 17.0.1)

Rule details

HighCVE-2026-1028022026-10-31

Articles Anywhere - Articles Anywhere (articlesanywhere) 19.0.0 to below 20.1.1 - Authenticated PHP Execution via Included Articles when Sourcerer is also installed

CVE-2026-102802 (published 2 Nov 2026, CVSS 4.0 8.9 High). When Regular Labs Sourcerer is installed alongside Articles Anywhere, an article included through an Articles Anywhere tag had its Sourcerer PHP run under the trust of the HOST article rather than its own author. A content author whose own articles are not trusted to run Sourcerer PHP could therefore get their PHP executed by having their article pulled into a trusted article (for example by a category or latest-articles listing). Sites without Sourcerer are not affected by this issue. The fix is joint: update Articles Anywhere to 20.1.1 or later AND Sourcerer to 17.0.1 or later (31 October 2026); updating only one of the two leaves the site exposed. Free and Pro editions are both affected. Temporary mitigation: restrict which user groups can create or edit articles, or disable Sourcerer PHP in articles until both extensions are updated.

Affected versions: ≥ 19.0.0 and < 20.1.1

Full advisory: our disclosure post

Our disclosure post

Other vulnerabilities in Articles Anywhere, Sourcerer, Articles Anywhere and Sourcerer

Updating for CVE-2026-102802 alone can leave a site on a release another rule still matches. These are the other flaws we check for in the same extensions.

Articles Anywhere

Latest safe version: 20.1.1

All 10 CVEs in Articles Anywhere

Sourcerer

Latest safe version: 17.0.1

Articles Anywhere

Latest safe version: 20.1.1

Sourcerer

Latest safe version: 17.0.1

References

CVE-2026-102802 questions

Which versions are affected by CVE-2026-102802?
CVE-2026-102802 is covered by 2 rules: Sourcerer from 13.0.0 up to but not including 17.0.1; Articles Anywhere from 19.0.0 up to but not including 20.1.1.
How do I fix CVE-2026-102802?
It depends on the extension and release line your site runs. For Sourcerer from 13.0.0 up to but not including 17.0.1: update Sourcerer to 17.0.1 or later. For Articles Anywhere from 19.0.0 up to but not including 20.1.1: update Articles Anywhere to 20.1.1 or later.
How severe is CVE-2026-102802?
Joomla CNA scores it 8.9 (High) under CVSS 4.0. In plain terms: reachable across the internet, needs an account with elevated rights and nobody has to be tricked into anything.

Running an affected version on a site you manage?

A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.

This check is part of the mySites.guru Joomla vulnerability scanner, which reads every installed extension's version on each audit. Browse the rest of the Joomla vulnerability database.

Rules current as of 21 November 2026.