CVE-2026-115479: baserCMS: Mail-form auto-replies accept multiple visitor-controlled recipients

Published Oct 23, 2026
·
Updated

baserCMS is a website development framework. In versions 5.2.5 before 5.3.2 and 5.4.0 before 5.4.2, an unauthenticated visitor can supply a comma-separated address list in a public mail form's email field and cause a single auto-reply to be addressed to multiple third parties. MailMessageMailer::sendFormToUser() passes the visitor-controlled userMail value to parseAndNormalizeMailAddresses(), which splits it with explode(',') and supplies every resulting address to setTo(). Newly created forms with an email-type field are affected when the separate, optional VALIDEMAIL server-side validation is not enabled; browser type=email validation does not prevent crafted requests. The bundled contact form enables VALIDEMAIL and is not affected. The auto-reply uses the site's sender identity and includes partially attacker-controlled content, allowing abuse of the site to deliver unsolicited mail. This issue has been patched in versions 5.3.2 and 5.4.2.

Affected Software

1 affected component
baserCMS BaserCMS>=5.2.5<5.3.2, >=5.4.0<5.4.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade baserCMS to a version that resolves this vulnerability.

    Fixed in 5.3.2
  2. Upgrade

    Upgrade baserCMS to a version that resolves this vulnerability.

    Fixed in 5.4.2
  3. Configuration

    Enable the separate, optional VALID_EMAIL server-side validation for email-type fields in newly created forms.

    baserCMS mail forms VALID_EMAIL = enabled

Event History

Oct 23, 2026
CVE Published
via MITRE·01:36 PM
Data Sourced
via MITRE·01:36 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Deployments running versions 5.2.5 before 5.3.2 or 5.4.0 before 5.4.2 are exposed only where a public mail form has an email-type field and does not enable the optional VALID_EMAIL server-side validation. The bundled contact form enables VALID_EMAIL and is not affected.

2

Does an attacker need an account or user interaction?

No. An unauthenticated visitor can submit a crafted request directly to an affected public mail form; browser type=email validation does not stop crafted requests.

3

What can an attacker do?

They can provide a comma-separated list of email addresses in the form's email field, causing one auto-reply to be sent to multiple third-party recipients. The messages use the site's sender identity and include partially attacker-controlled content.

4

What should be done if updating is not immediately possible?

Enable VALID_EMAIL server-side validation on every public mail form with an email-type field. This prevents the affected behavior described for forms that lack that optional validation.

5

How can we determine whether our forms are affected?

Review public mail forms for email-type fields and verify that VALID_EMAIL server-side validation is enabled. Forms with that validation enabled, including the bundled contact form, are not affected.

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