Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-30878: CWE-285: Improper Authorization in baserproject basercms

0
Medium
VulnerabilityCVE-2026-30878cvecve-2026-30878cwe-285
Published: Tue Mar 31 2026 (03/31/2026, 00:45:21 UTC)
Source: CVE Database V5
Vendor/Project: baserproject
Product: basercms

Description

CVE-2026-30878 is a medium severity improper authorization vulnerability in baserCMS versions prior to 5. 2. 3. It allows unauthenticated users to submit mail form entries via a public mail submission API even when the form is configured to reject submissions. This bypasses administrative controls designed to prevent form intake, enabling potential spam or abuse through the API. The vulnerability does not impact confidentiality or availability but compromises integrity by allowing unauthorized data submission. No user interaction or authentication is required, and exploitation can be performed remotely over the network. The issue has been patched in baserCMS version 5. 2. 3.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/31/2026, 01:25:45 UTC

Technical Analysis

CVE-2026-30878 identifies an improper authorization vulnerability (CWE-285) in baserCMS, a popular website development framework. The flaw exists in the mail submission API prior to version 5.2.3, where unauthenticated users can submit mail form entries even when the corresponding form is configured to disallow submissions. This bypass occurs because the API does not properly enforce administrative controls that disable form intake, allowing attackers to send arbitrary data through the mail submission endpoint. The vulnerability is remotely exploitable without requiring any authentication or user interaction, making it relatively easy to abuse. While it does not expose sensitive data or disrupt service availability, it compromises data integrity by permitting unauthorized form submissions, which can be leveraged for spam campaigns or other abusive activities. The issue was publicly disclosed and patched in version 5.2.3 of baserCMS. No known exploits have been reported in the wild to date. The CVSS v3.1 base score is 5.3, reflecting medium severity due to the ease of exploitation and impact on integrity without affecting confidentiality or availability.

Potential Impact

The primary impact of this vulnerability is the potential for spam and abuse through unauthorized mail form submissions. Organizations using vulnerable baserCMS versions may experience increased spam traffic, which can degrade user experience, overwhelm backend processing systems, and potentially lead to blacklisting of their domains or IP addresses. Although the vulnerability does not directly compromise confidential information or availability, the integrity of form data is undermined, which may affect business processes relying on accurate form submissions. Additionally, attackers could use this vector to inject malicious content or phishing messages, indirectly increasing risk to end users. The ease of exploitation and lack of authentication requirements mean that any publicly accessible baserCMS site with affected versions is at risk. This can lead to reputational damage and increased operational costs for mitigation and cleanup.

Mitigation Recommendations

The most effective mitigation is to upgrade baserCMS installations to version 5.2.3 or later, where the vulnerability has been patched. Until upgrade is possible, organizations should consider disabling or restricting access to the mail submission API endpoint, for example by implementing IP whitelisting or web application firewall (WAF) rules to block unauthorized requests. Monitoring and rate limiting mail form submissions can help detect and reduce abuse. Administrators should audit form configurations to ensure that forms intended to reject submissions are properly enforced at all layers. Logging and alerting on unusual submission patterns can provide early warning of exploitation attempts. Additionally, implementing CAPTCHA or other anti-bot mechanisms on forms can reduce automated abuse. Regular security assessments and keeping software up to date are critical to prevent exploitation of such vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-06T00:04:56.699Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69cb1e82e6bfc5ba1d9722b7

Added to database: 3/31/2026, 1:08:18 AM

Last enriched: 3/31/2026, 1:25:45 AM

Last updated: 3/31/2026, 3:16:06 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses