Tassos ACF and Smile Pack for Joomla Fix Two CVEs: a Map XSS and Gallery Image Deletion

TL;DR
Tassos has fixed two security flaws in the framework bundled with two of its Joomla extensions, Advanced Custom Fields and Smile Pack. The Joomla CNA published a CVE for each on 5 November 2026. CVE-2026-115452, scored CVSS 4.0 7.5 High, is a stored cross-site scripting (XSS) flaw in the Map field’s marker labels: a user who can edit a marker label can save a script that runs for everyone who opens the marker. CVE-2026-115451, scored 6.9 Medium, is an improper access control flaw in the Gallery field’s image removal: anyone could delete images in the Gallery folders without logging in.
The fixed versions are Advanced Custom Fields 3.1.9 for Joomla 4, 5 and 6 and 2.8.16 for Joomla 3, in Free and Pro packages, and Smile Pack 2.1.7 for Joomla 4 and later and 1.2.10 for Joomla 3. The ACF 3.1.9 and Smile Pack 2.1.7 releases came out on 4 November, the Joomla 3 builds on 5 November.
CVE-2026-115452Stored XSS in Map marker labels, ACF and Smile Pack
HighJoomla CNA
A user who can edit a Map marker label can save a script that runs for anyone who opens the marker.
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NWhat does this mean?
CVSS 4.0 scores how severe a flaw is, from 0 (no impact) to 10 (critical). Each pair of letters in the string above is one metric; here is what this one's says.
How it is reached
- AV:N
- Network: Reachable across the internet
- AC:L
- Low: Nothing to work around, it just works
- AT:P
- Present: Needs a particular deployment or race to line up
- PR:H
- High: Needs an account with elevated rights
- UI:N
- None: Nobody has to be tricked into anything
What it does to the site
- VC:H
- High: Everything the site holds can be read
- VI:H
- High: Data and files can be altered at will
- VA:L
- Low: The site slows or stutters
What it does beyond the site
- SC:N
- None: Other systems keep their data
- SI:N
- None: Other systems keep their integrity
- SA:N
- None: Other systems stay up
CVE-2026-115451Unauthenticated image deletion in Gallery folders, ACF Pro and Smile Pack
MediumJoomla CNA
Anyone could delete images in the Gallery folders without logging in, including images on published articles and modules.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NWhat does this mean?
CVSS 4.0 scores how severe a flaw is, from 0 (no impact) to 10 (critical). Each pair of letters in the string above is one metric; here is what this one's says.
How it is reached
- AV:N
- Network: Reachable across the internet
- AC:L
- Low: Nothing to work around, it just works
- AT:N
- None: Works against any affected install
- PR:N
- None: No account needed
- UI:N
- None: Nobody has to be tricked into anything
What it does to the site
- VC:L
- Low: Some data can be read
- VI:L
- Low: Some data can be altered
- VA:N
- None: The site stays up
What it does beyond the site
- SC:N
- None: Other systems keep their data
- SI:N
- None: Other systems keep their integrity
- SA:N
- None: Other systems stay up
These are Joomla extensions by Tassos Marinos. They have nothing to do with Advanced Custom Fields for WordPress, or with the ACF Extended add-on for WordPress that has been in the vulnerability feeds all week with an unauthenticated remote code execution flaw. The two are compared below.
Not the WordPress plugin
Advanced Custom Fields for Joomla is a Tassos extension. Advanced Custom Fields for WordPress is a WP Engine plugin, and Advanced Custom Fields: Extended is a third-party add-on to it with its own CVEs this week. Same name, different CMS, different vendor, no shared code.
The Map Field Marker Label XSS, CVE-2026-115452
The Map field in ACF for Joomla lets an editor drop markers on a map, each with a label and an address. Before 3.1.9 those labels and addresses were output as saved, with no filtering. That is a stored cross-site scripting flaw: a label containing a script tag or an event handler is saved once and then runs in the browser of every visitor who views the item, and of every administrator who opens it in the back end. The Joomla CNA scores it CVSS 4.0 7.5 High, and the record credits no one and says nothing about exploitation.
Who can plant it is whoever can edit an item with a Map field on it: an article, a user profile or any other item with ACF fields. On most sites that is a content editor, which is a lower bar than Super User. Front-end editing and user profile fields push the bar lower still. The payoff for an attacker is the usual one for stored XSS, which is the session of whoever views the marker, and the administrator’s session is the valuable one. We wrote up the same class of flaw in Phoca Gallery’s EXIF data.
In 3.1.9, marker labels and addresses go through Joomla’s InputFilter, which strips scripts and event handlers while allowing harmless HTML such as links. The change is in the Tassos Framework bundled with ACF (the system plugin “nrframework”), which moves from 6.1.39 to 6.1.51. The Map field plugin itself only changed its version headers. Tassos describes the change as “Fixed a security flaw in the Map field’s marker labels” and does not use the term XSS; that is our description of what the change fixes. The Map field is in Free and Pro, so every edition is affected.
The Gallery Field Image Deletion, CVE-2026-115451
The Gallery field is only in ACF Pro. Tassos’s release notes say that 3.1.9 “Fixed a security flaw in the Gallery field’s image removal” and nothing more. The CVE record has the detail. In the Joomla CNA’s words: “Anyone could delete images in the Gallery folders, including images on published articles and modules, without logging in. In ACF 3.1.7 and 3.1.8, users could also see, remove or save each other’s unsaved uploads.” It is filed as improper access control (CWE-284) and scored CVSS 4.0 6.9 Medium, with Michael Nielsen credited as the finder.
The score is lower than the Map flaw because the damage stops at deleted files, but the bar is lower too: it needs no account at all. An attacker who deletes a Gallery image removes it from every published article and module that used it, so the visible result on a site is broken images rather than a takeover. The cross-user part, where one logged-in user could see, remove or save another’s unsaved uploads, applies to ACF 3.1.7 and 3.1.8 only. It matches a line in the 3.1.9 notes that Tassos lists as a plain bug fix, “Fixed the Gallery field showing images that another user uploaded but had not saved yet”.
The framework code, which is in the Free package too, fits the record. 3.1.9 adds a check that an image can only be removed or processed for a gallery when it is one of that gallery’s stored images or the current user’s own pending upload. The removal endpoint rejects a plain file path and deletes only files the server issued a token for. Pending uploads now live in a temp folder scoped to the user who uploaded them, and path traversal in the image path is rejected. The same release also stops Gallery uploads that were never saved from staying in Joomla’s temporary folder.
Which ACF for Joomla Versions Are Affected?
The two CVEs have different ranges. CVE-2026-115452, the Map flaw, lists ACF 3.0.0 to 3.1.8 and 2.8.2 to 2.8.15. CVE-2026-115451, the Gallery flaw, lists 3.1.4 to 3.1.8 and 2.8.13 to 2.8.15, with the cross-user unsaved uploads part on 3.1.7 and 3.1.8 only. Tassos gives no first affected version for either flaw, so treat anything older than 2.8.2 as needing the update too.
| ACF for Joomla version | Flaws | What to do |
|---|---|---|
| 3.1.9 | Fixed (Joomla 4, 5, 6) | Nothing |
| 3.1.4 to 3.1.8 | Map XSS (CVE-2026-115452) and Gallery deletion (CVE-2026-115451) | Update to 3.1.9 |
| 3.1.1 to 3.1.3 | Map XSS only | Update to 3.1.9 |
| 3.0.0 to 3.1.0 | Map XSS, and in range of the March framework flaw | Update to 3.1.9 and review the site |
| 2.8.16 | Fixed (Joomla 3) | Nothing |
| 2.8.13 to 2.8.15 | Map XSS and Gallery deletion, and in range of the March framework flaw | On Joomla 3, update to 2.8.16 and review the site; on Joomla 4 or later, update to 3.1.9 |
| 2.2.0 to 2.8.12 | Map XSS, and in range of the March framework flaw | On Joomla 3, update to 2.8.16 and review the site; on Joomla 4 or later, update to 3.1.9 |
| Below 2.2.0 | Treat as affected | 2.8.16 on Joomla 3, 3.1.9 on Joomla 4 or later |
Check the version on the System - ACF plugin (plg_system_acf). The individual ACF field plugins all report 1.0, whatever release you run. That catches people out when they look at the Map field plugin in particular, because the fix is in the framework and the Map field plugin only changed its version headers.
The framework is shared, and any Tassos extension can install a newer copy of it. A site that updated another Tassos extension recently may already have framework 6.1.51 while ACF itself still reads 3.1.8. Update ACF to 3.1.9 anyway, so the ACF plugins and the framework match and the site stops showing as affected.
ACF 2.8.16 for Joomla 3
Advanced Custom Fields has two release lines. The 3.x line has needed Joomla 4 or later since 3.0.0 in July 2025, and the 2.8.x line is the legacy release Tassos still builds for Joomla 3.8 to 3.10. The 4 November fix only reached the 3.x line, and ACF 2.8.16 followed on 5 November for Joomla 3.
Its release notes repeat the 3.1.9 security lines word for word, and the fix sits in the same place. The Joomla 3 build of the Tassos Framework moves from 6.1.1-j3 to 6.1.3-j3, Map marker labels and addresses now go through Joomla’s InputFilter, and the Gallery removal endpoint now rejects a plain file path and deletes only files the server issued a token for. Nothing in the field plugins changed apart from version headers, as with 3.1.9.
Most ACF sites below 3.0 that we monitor run Joomla 3. The few that run Joomla 4 or 5 on an old 2.x release should go straight to 3.1.9, not 2.8.16. For the other extensions on a Joomla 3 site, joomla3security.com lists what Tassos and other vendors still patch.
How Fast the Joomla 4+ Sites Updated
Connected Joomla sites running Advanced Custom Fields in the mySites.guru database, measured at 12:23 UTC on 4 November and 09:40 UTC on 5 November 2026.
Smile Pack Has the Same Two Flaws
Smile Pack is Tassos’s collection of Joomla modules, and it bundles the same framework code as ACF. Its Map module has the same marker label flaw and its Gallery module the same image deletion flaw, and both CVEs name it. Smile Pack 2.1.7, released on 4 November 2026 alongside ACF 3.1.9, lists both fixes in the same words: “Fixed a security flaw in the Gallery module’s image removal” and “Fixed a security flaw in the Map module’s marker labels”. The Joomla 3 build, 1.2.10, followed on 5 November.
The ranges follow the same pattern as ACF. CVE-2026-115452 covers Smile Pack 2.0.0 to 2.1.6 and 1.1.2 to 1.2.9; CVE-2026-115451 covers 2.1.2 to 2.1.6 and 1.2.7 to 1.2.9. About half of the Smile Pack 2.x sites we monitor had already moved to 2.1.7 by the evening of 5 November, through ordinary updates.
| Smile Pack version | Flaws | What to do |
|---|---|---|
| 2.1.7 | Fixed (Joomla 4, 5, 6) | Nothing |
| 2.1.2 to 2.1.6 | Map XSS (CVE-2026-115452) and Gallery deletion (CVE-2026-115451) | Update to 2.1.7 |
| 2.0.0 to 2.1.1 | Map XSS only | Update to 2.1.7 |
| 1.2.10 | Fixed (Joomla 3) | Nothing |
| 1.2.7 to 1.2.9 | Map XSS and Gallery deletion | Update to 1.2.10 on Joomla 3, 2.1.7 on Joomla 4 or later |
| 1.1.2 to 1.2.6 | Map XSS only | Update to 1.2.10 on Joomla 3, 2.1.7 on Joomla 4 or later |
Check the version on the Smile Pack component (com_smilepack). The modules and the system plugin all report 1.0.0, whatever release you run.
Joomla’s ACF Is Not WordPress’s ACF
Three products share the name, and this week two of them have security news. The Tassos extension is the Joomla one. The ACF Extended CVEs are the WordPress ones.
| Product | CMS | Made by | This week’s news | What to do |
|---|---|---|---|---|
| Advanced Custom Fields (Tassos) | Joomla | Tassos Marinos | 3.1.9 and 2.8.16 fix a Map marker XSS, CVE-2026-115452 (7.5), and Gallery image deletion, CVE-2026-115451 (6.9) | Update to 3.1.9, or 2.8.16 on Joomla 3 |
| Advanced Custom Fields | WordPress | WP Engine | No new CVE found this week | Keep updated as usual |
| Advanced Custom Fields: Extended (and PRO) | WordPress | ACF Extended (third-party add-on) | A dozen CVEs since 20 October, incl. unauthenticated RCE CVE-2026-120534 (9.8) | Update ACF Extended to latest |
Scanners, news headlines and vulnerability feeds all shorten the name to “ACF”, so the two get mixed up. A Joomla agency reads “ACF unauthenticated RCE” and panics; a WordPress agency reads “ACF 3.1.9 security release” and goes looking for a version that does not exist on their platform. If you run Joomla, the WordPress CVEs do not apply to you. If you run WordPress, the Tassos release does not apply to you. Agencies with both get both.
On the WordPress side, CVE-2026-120534, published on 3 November 2026 by Wordfence, is an unauthenticated remote code execution flaw in Advanced Custom Fields: Extended PRO up to 0.9.2.6, via the Dynamic Render field type, scored CVSS 3.1 9.8. Before that, on 23 October, WPScan published CVE-2026-94262 and CVE-2026-94268, unauthenticated takeover of non-administrator and administrator accounts through the front-end user update action in 0.9.2.7, fixed in 0.9.2.8, plus CVE-2026-94263, unauthenticated arbitrary shortcode execution via a form success message in 0.9.2.4 to 0.9.2.7. On 27 October Wordfence added CVE-2026-10752, unauthenticated arbitrary attachment deletion up to 0.9.2.6. Our WordPress feed holds eleven ACF Extended CVEs published between 20 and 30 October, plus the 3 November PRO one. Update ACF Extended and ACF Extended PRO to the latest release. We covered ACF Extended’s earlier 9.8 flaw, CVE-2025-13486 when it was being exploited.
What To Do Now
- Update Advanced Custom Fields, Free or Pro, to 3.1.9 on every Joomla 4, 5 or 6 site and to 2.8.16 on every Joomla 3 site, through Joomla’s Update tab or the mySites.guru mass updater.
- Update Smile Pack to 2.1.7 on Joomla 4, 5 or 6 and to 1.2.10 on Joomla 3.
- Confirm the versions afterwards on the System - ACF plugin (plg_system_acf) and the Smile Pack component (com_smilepack), not on the field plugins or modules.
- If you let anyone other than trusted staff edit items with Map fields (front-end editing, user profile fields), open the Map fields on those items and look at the marker labels and addresses for script.
- On ACF Pro sites with Gallery fields, and Smile Pack sites with the Gallery module, check that the images on published articles and modules are still there.
- Check administrator accounts. A stored XSS that ran in an administrator’s browser can end with an account you did not create.
Find administrator accounts you never created
mySites.guru checks every connected site for this automatically and flags it the moment it appears. It runs as part of the full audit on every connected site.
How mySites.guru Flags ACF on Joomla and WordPress
mySites.guru flags every connected Joomla site running Advanced Custom Fields below its fixed release, with one rule per release line: ACF 3.x below 3.1.9, and ACF 2.x and older below 2.8.16. The version is read from the ACF system plugin, plg_system_acf, for the reason above. Two more rules cover Smile Pack, read from com_smilepack: 2.x below 2.1.7 and 1.x below 1.2.10. Those four rules are for CVE-2026-115452 and are rated High. Four further rules cover CVE-2026-115451 at the CVE’s exact ranges, ACF 3.1.4 to 3.1.8 and 2.8.13 to 2.8.15 and Smile Pack 2.1.2 to 2.1.6 and 1.2.7 to 1.2.9, and are rated Medium. They are kept separate because the flaw, the login requirement and the range all differ, so a site on ACF 3.1.2 shows only the Map flaw and a site on 3.1.8 shows both. The flags work the same way as every other entry in our vulnerable extension list, alongside the security release flag on extension updates.
The WordPress side is covered from the same dashboard. Our WordPress vulnerability feed is imported from Wordfence, so the ACF Extended CVEs flag connected WordPress sites automatically, with no rule to write by hand. An agency running Joomla sites with Tassos ACF and WordPress sites with ACF Extended sees both lists in one place, and the mass updater pushes both updates. Every rule we hold is listed on the public vulnerabilities page, and all of this is part of the subscription.
The Last Tassos Security Release
This is the second Tassos security release this year that touches ACF. In March, CVE-2026-21627 in the Novarain/Tassos Framework was an unauthenticated file inclusion, deletion and SQL injection flaw scored CVSS 9.5, and ACF was one of the extensions bundling it. That one was fixed long ago and is a different flaw, but the pattern is the same: the framework is where the fix lives, and every Tassos extension that bundles it picks up the change. If a site skipped the March update, 3.1.9 is the moment to catch up on both.
Novarain Framework Vulnerability: Check Your Joomla Sites for nrframeworkRead the full postIf a site has already been hit, or you would rather someone else made sure, fix.mySites.guru patches the site, audits it for backdoors and hands it back secure for a single fixed fee, usually the same day.
Timeline
Two CVE ids reserved
The Joomla CNA reserves CVE-2026-115451 and CVE-2026-115452, per the reserved dates on the records.
Tassos releases ACF 3.1.9 and Smile Pack 2.1.7
The Joomla 4, 5 and 6 builds fix a stored XSS in Map marker labels and an image deletion flaw in Gallery image removal.
mySites.guru flags ACF sites
Rules are added for every connected Joomla site on ACF below 3.1.9.
Tassos releases the Joomla 3 builds
ACF 2.8.16 and Smile Pack 1.2.10 are released with the same two fixes for Joomla 3 sites.
mySites.guru splits the ACF rule per release line
Joomla 3 sites on ACF 2.8.16 now show as fixed rather than as below 3.1.9.
Joomla CNA publishes both CVE records
CVE-2026-115452 covers the Map marker XSS at CVSS 4.0 7.5 High with no finder credited, and CVE-2026-115451 covers the Gallery image deletion at 6.9 Medium, credited to Michael Nielsen.
mySites.guru adds Smile Pack rules
Rules are added for connected sites on Smile Pack below 2.1.7, or below 1.2.10 on Joomla 3, and both CVE ids are attached to the ACF and Smile Pack rules.
Further Reading
- Tassos: Advanced Custom Fields 3.1.9 - the vendor's release page for Joomla 4 to 6.
- Tassos: Advanced Custom Fields 2.8.16 - the vendor's release page for Joomla 3.
- CVE-2026-115452 - the Joomla CNA record for the Map marker label flaw in ACF and Smile Pack.
- CVE-2026-115451 - the Joomla CNA record for the Gallery image deletion flaw in ACF and Smile Pack.
- Tassos: Smile Pack changelog - the vendor's notes for Smile Pack 2.1.7.
- Tassos on joomla3security.com - every Tassos extension's Joomla 3 position and backported fixes.
- Tassos Framework Flaw in March: CVE-2026-21627 - the earlier 9.5 Critical flaw in the framework ACF bundles.
- Ajax Endpoints: The CMS Security Blind Spot - covers ACF Extended for WordPress and its earlier CVE-2025-13486.
- CVE-2026-120534 - the ACF Extended PRO for WordPress remote code execution record.
- OWASP: Cross Site Scripting (XSS) - how stored XSS works and why output filtering stops it.



