CVE-2026-30878: Baserproject/basercms BaserCMS Has Mail Form Acceptance Vulnerability

MODERATE
Advisory Identifier: GHSA-8cr7-r8qw-gp3c
CVSS 5.3
CWE-285
Published
Advisory Summary

CVE-2026-30878 is a MODERATE (CVSS 5.3) basercms has mail form acceptance vulnerability (CWE-285: Improper Authorization) affecting Baserproject/basercms libraries in the Packagist ecosystem. The issue involves basercms has mail form acceptance bypass via public api. Remediation is available by upgrading affected packages to version 5.2.3.

CVE-2026-30878 at a Glance

CVE Identifier CVE-2026-30878
GHSA Identifier GHSA-8cr7-r8qw-gp3c
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-285: Improper Authorization
Affected Product Baserproject/basercms
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-30878

To remediate this vulnerability, upgrade all affected Baserproject/basercms dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

baserproject/basercms fixed: 5.2.3
Upgrade baserproject/basercms to 5.2.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for baserproject/basercms

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-30878, inspect your project dependencies for Baserproject/basercms:

inspect dependencies for baserproject/basercms

Analyze the terminal output to locate any version of Baserproject/basercms in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.2.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Baserproject/basercms, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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/basercms_cookies.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/mail_messages/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/basercms_cookies.txt --data-urlencode 'name_1=Test' --data-urlencode 'name_2=User' --data-urlencode 'email_1=test@example.com' --data-urlencode 'email_2=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.

CVE-2026-30878 Affected Baserproject/basercms Versions

1 component(s)
Fixed Versions:
5.2.3
Product / Package Ecosystem Affected Versions Fixed Version
baserproject/basercms
Packagist
< 5.2.3
5.2.3

References

Frequently Asked Questions

What is CVE-2026-30878?
CVE-2026-30878 is a security vulnerability in Baserproject/basercms involving baserCMS has Mail Form Acceptance Bypass via Public API under CWE-285: Improper Authorization.
Which Baserproject/basercms versions are affected?
Affected versions include releases prior to 5.2.3 across affected packages: baserproject/basercms.
What version fixes CVE-2026-30878?
Upgrading to 5.2.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is baserproject/basercms affected?
Yes, baserproject/basercms is affected in releases prior to 5.2.3. Upgrade your dependency to 5.2.3 or later.
What is the CVSS score of CVE-2026-30878?
CVE-2026-30878 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-30878?
CVE-2026-30878 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Packagist dependencies for CVE-2026-30878?
Run the dependency tree command: 'inspect dependencies for baserproject/basercms'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8cr7-r8qw-gp3c",
  "modified" : "2026-03-31T22:36:18Z",
  "published" : "2026-03-31T22:36:18Z",
  "aliases" : [ "CVE-2026-30878" ],
  "summary" : "baserCMS has Mail Form Acceptance Bypass via Public API",
  "details" : "### Summary\nA 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.\n\n### Details\nIn 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).\n\nThese checks are enforced in the UI flow handled by `MailController::index()` and `MailController::confirm()`  \n(e.g. `plugins/bc-mail/src/Controller/MailController.php`).\n\nHowever, the public API endpoint:\n\n`plugins/bc-mail/src/Controller/Api/MailMessagesController.php::add()`\n\ndoes 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.\n\nThe 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.\n\n### PoC\n1. In the admin UI, configure a mail form so that it is **not accepting submissions** (e.g. outside its acceptance period or explicitly closed).\n2. Obtain a CSRF cookie by accessing the site root:\n```\ncurl -sS -D - -o - -c /tmp/basercms_cookies.txt 'http://localhost/'\n```\n3. Extract the CSRF token from the `csrfToken` cookie and submit a POST request to the public API endpoint:\n```\ncurl -sS -D - -o - -X POST 'http://localhost/baser/api/bc-mail/mail_messages/add/1.json' \n-H 'Content-Type: application/x-www-form-urlencoded' \n-H 'Referer: http://localhost/' \n-H 'X-CSRF-Token: <csrf-token-from-cookie>' \n-b /tmp/basercms_cookies.txt \n--data-urlencode 'name_1=Test' \n--data-urlencode 'name_2=User' \n--data-urlencode 'email_1=test@example.com' \n--data-urlencode 'email_2=test@example.com' \n--data-urlencode 'category[]=資料請求' \n--data-urlencode 'root=検索エンジン' \n--data-urlencode 'message=API bypass test'\n```\n4. The server responds with `200 OK` and creates a mail message, even though the form is configured to reject submissions.\n\n### Impact\nThis is an access control / business logic bypass vulnerability.\n\nAdministrators 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "baserproject/basercms"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.2.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.2.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/baserproject/basercms/security/advisories/GHSA-8cr7-r8qw-gp3c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30878"
  }, {
    "type" : "WEB",
    "url" : "https://basercms.net/security/JVN_20837860"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/baserproject/basercms"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/baserproject/basercms/releases/tag/5.2.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-31T22:36:18Z",
    "nvd_published_at" : "2026-03-31T01:16:35Z"
  }
}