CVE-2026-30878: baserCMS: Mail Form Acceptance Bypass via Public API

Published Mar 31, 2026
·
Updated

Summary A public mail submission API allows unauthenticated users to submit mail form entries even when the corresponding form is not accepting submissions. This bypasses administrative controls intended to stop form intake and enables spam or abuse via the API.

Details In baserCMS, mail form submissions through the front-end UI are guarded by acceptance checks implemented in MailFrontService::isAccepting(), which ensures that the mail form is currently accepting submissions (e.g. within its configured publish/acceptance window).

These checks are enforced in the UI flow handled by MailController::index() and MailController::confirm() (e.g. plugins/bc-mail/src/Controller/MailController.php).

However, the public API endpoint:

plugins/bc-mail/src/Controller/Api/MailMessagesController.php::add()

does not invoke MailFrontService::isAccepting() and does not verify whether the mail form is currently accepting submissions. As a result, the API accepts submissions regardless of the form’s acceptance state.

The endpoint does not require authentication. A valid CSRF cookie and token pair is sufficient to create a mail message. This allows submissions even when administrators intentionally disable or close the mail form via the admin UI.

PoC 1. In the admin UI, configure a mail form so that it is not accepting submissions (e.g. outside its acceptance period or explicitly closed). 2. Obtain a CSRF cookie by accessing the site root: curl -sS -D - -o - -c /tmp/basercmscookies.txt 'http://localhost/' 3. Extract the CSRF token from the csrfToken cookie and submit a POST request to the public API endpoint: curl -sS -D - -o - -X POST 'http://localhost/baser/api/bc-mail/mailmessages/add/1.json' -H 'Content-Type: application/x-www-form-urlencoded' -H 'Referer: http://localhost/' -H 'X-CSRF-Token: <csrf-token-from-cookie>' -b /tmp/basercmscookies.txt --data-urlencode 'name1=Test' --data-urlencode 'name2=User' --data-urlencode 'email1=test@example.com' --data-urlencode 'email2=test@example.com' --data-urlencode 'category[]=資料請求' --data-urlencode 'root=検索エンジン' --data-urlencode 'message=API bypass test' 4. The server responds with 200 OK and creates a mail message, even though the form is configured to reject submissions.

Impact This is an access control / business logic bypass vulnerability.

Administrators rely on the mail form acceptance settings to temporarily or permanently stop form intake (e.g. during maintenance, incidents, or spam attacks). This vulnerability allows attackers to bypass those controls via the public API, enabling unauthorized mail submissions, spam, and operational disruption.

Other sources

baserCMS is a website development framework. Prior to version 5.2.3, a public mail submission API allows unauthenticated users to submit mail form entries even when the corresponding form is not accepting submissions. This bypasses administrative controls intended to stop form intake and enables spam or abuse via the API. This issue has been patched in version 5.2.3.

— MITRE

Affected Software

3 affected componentsFixes available
baserCMS BaserCMS<5.2.3
composer/baserproject/basercms<=5.2.2
5.2.3
baserCMS BaserCMS<5.2.3

Event History

Mar 31, 2026
CVE Published
via MITRE·12:45 AM
Data Sourced
via MITRE·12:45 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·10:36 PM
Data Sourced
via GitHub·10:36 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-30878?

CVE-2026-30878 has a medium severity rating due to its potential to allow unauthorized email submissions.

2

How do I fix CVE-2026-30878?

To resolve CVE-2026-30878, upgrade baserCMS to version 5.2.3 or later.

3

What type of vulnerability is CVE-2026-30878?

CVE-2026-30878 is an authentication bypass vulnerability affecting the mail submission functionality.

4

Who is affected by CVE-2026-30878?

Users of baserCMS prior to version 5.2.3 are affected by CVE-2026-30878.

5

Can CVE-2026-30878 lead to data exposure?

Yes, CVE-2026-30878 can lead to unintended exposure of email form data due to unauthorized submissions.

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