CVE-2026-55572: e107: SQL injection in alt_auth plugin (otherdb / e107db backends) via login username

Published Oct 14, 2026
·
Updated

e107 is a content management system (CMS). Prior to 2.3.7, the bundled altauth plugin's otherdb and e107db authentication backends interpolate the submitted login username directly into SQL in e107plugins/altauth/otherdbauth.php and e107plugins/altauth/e107dbauth.php. The login() methods execute those strings with PDO::query() before effective sanitization, so an unauthenticated user can inject SQL when altauth is installed and either backend is configured with a live external database connection. The injection can expose or modify data available to the configured database account, and query failures can additionally disclose the generated query through the debug-message path. This issue is fixed in version 2.3.7.

Affected Software

1 affected component
e107 e107<2.3.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade e107 to a version that resolves this vulnerability.

    Fixed in 2.3.7

Event History

Oct 14, 2026
CVE Published
via MITRE·06:12 PM
Data Sourced
via MITRE·06:12 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to unauthenticated exploitation?

Deployments prior to 2.3.7 are exposed if the bundled alt_auth plugin is installed and either the otherdb or e107db backend is configured with a live external database connection. The attacker does not need an account or user interaction; they only need to submit a crafted login username.

2

Is this affected by the default authentication configuration?

The issue is limited to the alt_auth plugin's otherdb and e107db backends. The provided information does not indicate that installations using other authentication backends are affected.

3

What is the immediate mitigation if upgrading is not possible?

Disable the affected alt_auth backend or remove its live external database connection until the instance can be updated. This prevents the vulnerable login methods from querying the external database with an attacker-controlled username.

4

What could indicate attempted exploitation or information disclosure?

Review login-related failures and debug-message output for generated SQL queries, since query failures can disclose the constructed query through the debug-message path. Also investigate unexpected database reads or modifications performed by the account configured for the external authentication database.

5

What version contains the fix?

The issue is fixed in e107 version 2.3.7. Upgrade affected deployments to that version or later.

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