CVE-2026-115481 — baserCMS: BcCustomContent file fields can be configured to allow executable file extensions such as php, leading to arbitrary PHP file upload
baserCMS is a website development framework. Starting in version 5.0.0-beta1 and prior to versions 5.3.2 and 5.4.2, `PermissionGroupsService::build()` reads a plugin's `config/permission.php` to decide what each user group may reach. When that file is absent it writes a wildcard allow rule instead: `url` `/baser/<prefix>/<plugin>/*`, `method` `*`, `auth` true, for every non-admin group. BcCustomContent has no such file in any release. After an administrator installs it, the default `operators` group can store and execute arbitrary PHP under the document root. Versions 5.3.2 and 5.4.2 patch the issue.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Baserproject Basercms).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Baserproject | Basercms | version >= 5.0.0-beta1, < 5.3.2version >= 5.4.0, < 5.4.2 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.5 | CVSS 4.0 | High | — | — | security-advisories@github.com via NIST National Vulnerability Database |
| 8.5 | CVSS 4.0 | High | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 24, 2026 → Oct 30, 2026 · 7 reading(s) · max 0.47%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Deferred
- SSVC assessment updated
- Affected products added · baserproject/basercms
- Record published
- CVSS changed · 8.5
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 23, 2026 – Oct 23, 2026
- 1× Official description updated · Oct 23, 2026 – Oct 23, 2026
References
5 on the record
- github.com/baserproject/basercms/security/advisories/GHSA-8jrp-4h7c-m679
- github.com/baserproject/basercms/releases/tag/5.3.2
- github.com/baserproject/basercms/commit/2ed19c878add5c26fc765572e0e77173c1f1fdb5
- github.com/baserproject/basercms/commit/b0ef31b10dc6267b48ebc9a80d34bc7c4c09c311
- github.com/baserproject/basercms/releases/tag/5.4.2
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-115479 baserCMS: Mail-form auto-replies accept multiple visitor-controlled recipients 7d
- Medium CVE-2026-115480 baserCMS: Public Web API mail-form submission bypasses image CAPTCHA 7d
- High CVE-2026-114624 baserCMS: PHP object injection via unguarded unserialize() in the widget-area entity 7d
- High CVE-2026-115457 baserCMS: Unauthenticated Stored XSS via Shortcode Expansion in Blog Comments 7d
- Medium CVE-2026-114623 baserCMS: Path traversal in the BcThemeFile admin screen allows file disclosure 7d
- High CVE-2026-114621 baserCMS: SQL injection in the admin panel and admin API 7d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-115481 is "baserCMS: BcCustomContent file fields can be configured to allow executable file extensions such as php, leading to arbitrary PHP file upload", rated High. It affects Basercms (Baserproject); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.5 describes technical severity. EPSS 0.40% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.