CVE-2026-30878
Received Received - Intake
Unauthenticated Mail Submission Bypass in baserCMS API Prior to

Publication date: 2026-03-31

Last updated on: 2026-04-01

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-31
Last Modified
2026-04-01
Generated
2026-05-07
AI Q&A
2026-03-31
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
basercms basercms to 5.2.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows unauthenticated users to submit mail form entries even when the form is disabled, bypassing administrative controls. While it does not directly impact confidentiality or availability, it enables unauthorized mail submissions that can lead to spam or operational disruption.

Such unauthorized submissions could potentially interfere with compliance requirements related to data integrity and operational controls under standards like GDPR or HIPAA, especially if the spam or abuse leads to disruption of normal business processes or incident response.

However, since the vulnerability does not result in confidentiality breaches or data leaks, its direct impact on compliance with data protection regulations is limited.


Can you explain this vulnerability to me?

CVE-2026-30878 is a moderate severity vulnerability in baserCMS versions up to 5.2.2. It involves a mail form acceptance bypass via a public API. The public mail submission API endpoint does not check whether the mail form is currently accepting submissions, unlike the front-end UI controllers which perform this check.

Because of this missing verification, unauthenticated users can submit mail form entries even when the form is disabled or outside its acceptance period. This bypasses administrative controls intended to stop form intake.

The API endpoint requires no authentication beyond a valid CSRF cookie and token, allowing attackers to submit unauthorized mail messages, potentially leading to spam or abuse.


How can this vulnerability impact me? :

This vulnerability allows attackers to submit unauthorized mail form entries even when the form is disabled, which can lead to spam attacks or abuse via the API.

It can also interfere with operational procedures such as maintenance or incident response by bypassing administrative controls designed to stop form intake.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves unauthorized mail submissions via the public mail submission API endpoint in baserCMS versions up to 5.2.2. Detection can focus on monitoring traffic to the API endpoint related to mail submissions, specifically the endpoint at plugins/bc-mail/src/Controller/Api/MailMessagesController.php::add().

You can detect potential exploitation by inspecting HTTP requests to this API endpoint for mail form submissions occurring when the form is supposed to be disabled or outside its acceptance period.

  • Use network monitoring tools (e.g., tcpdump, Wireshark) to capture HTTP POST requests to the mail submission API endpoint.
  • Use web server logs (e.g., Apache or Nginx access logs) to search for POST requests to the mail submission API path.
  • Example command to search web server logs for suspicious mail submissions: grep -i 'POST /plugins/bc-mail/api/mail_messages/add' /var/log/nginx/access.log
  • Look for requests that include valid CSRF tokens but occur when the form should be disabled, indicating bypass attempts.

What immediate steps should I take to mitigate this vulnerability?

The primary mitigation is to upgrade baserCMS to version 5.2.3 or later, where this vulnerability has been patched.

Until the upgrade can be applied, consider restricting access to the mail submission API endpoint by implementing additional access controls such as IP whitelisting, authentication, or firewall rules to block unauthorized requests.

Monitor and audit mail submissions to detect and respond to any unauthorized or spam submissions.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart