CVE-2026-85188: Joomla Extension - regularlabs.com - Database data disclosure in Advanced Module Manager (Free, Pro) < 12.1.0, Conditional Content (Free, Pro) < 8.0.0, Content Templater (Pro) < 14.2.0, ReReplacer (Pro) < 16.2.0 for Joomla

Published Sep 14, 2026
·
Updated

Joomla Extension - regularlabs.com - Database data disclosure in Advanced Module Manager (Free, Pro) < 12.1.0, Conditional Content (Free, Pro) < 8.0.0, Content Templater (Pro) < 14.2.0, ReReplacer (Pro) < 16.2.0 for Joomla - The Conditions editor creates a default Condition Set name from the item to which the set is linked. The affected code accepts the database table and label-column names from the request. Although these names are quoted as SQL identifiers, they are not restricted to the tables and columns used by supported Regular Labs integrations. An attacker can therefore select a valid but unrelated database field. This is an authorization failure rather than SQL injection.

Affected Software

4 affected components
Joomla Extension - regularlabs.com - Advanced Module Manager (Free, Pro)<12.1.0
Joomla Extension - regularlabs.com - Conditional Content (Free, Pro)<8.0.0
Joomla Extension - regularlabs.com - Content Templater (Pro)<14.2.0
Joomla Extension - regularlabs.com - ReReplacer (Pro)<16.2.0

Event History

Sep 14, 2026
CVE Published
via MITRE·06:12 AM
Data Sourced
via MITRE·06:12 AM
DescriptionWeakness

Frequently Asked Questions

1

Which installations are affected?

Affected versions are Advanced Module Manager Free and Pro before 12.1.0, Conditional Content Free and Pro before 8.0.0, Content Templater Pro before 14.2.0, and ReReplacer Pro before 16.2.0.

2

What does an attacker need to exploit this issue?

The attacker must be able to submit request-controlled database table and label-column names to the Conditions editor. The issue occurs because those identifiers are not limited to tables and columns used by supported Regular Labs integrations.

3

What data could be exposed?

An attacker can select a valid but unrelated database field, potentially disclosing data through the default Condition Set name generation. The available information does not identify specific tables, fields, or records that can be accessed.

4

Is this SQL injection?

No. The database table and column names are quoted as SQL identifiers; the issue is an authorization failure that permits selection of unrelated valid fields rather than SQL injection.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203