Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to baserCMS with low-privilege account
-
DeliverySubmit input bypassing script validation filter
-
ExploitStore crafted XSS payload
-
ExecutionVictim loads affected page
-
PersistScript executes in victim browser context
-
ImpactSession/data compromise in victim origin
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated baserCMS account (PR:L) able to submit content that passes through the affected input path, plus the ability to craft a payload that bypasses baserCMS's script validation filter. Execution is limited by required victim user interaction (UI:R) - a second user must load the page hosting the injected script - and by the prior-authentication requirement, so this is not remotely exploitable against an unauthenticated attacker. Realistic risk is further limited by the small deployment base of baserCMS and the absence of any public exploit code. |
| Impact | This is a stored/validation-bypass XSS in baserCMS scored CVSS 3.0 5.4 (medium) with vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. The signals are internally consistent and modest: network vector with low complexity, but exploitation requires an authenticated actor (PR:L) and victim interaction (UI:R), and the impact is limited to low confidentiality and low integrity with no availability effect. The scope change (S:C) reflects script executing in the victim's browser context distinct from the vulnerable component, which is standard for reflected/stored XSS. No EPSS score, no CISA KEV listing, and no public proof-of-concept were provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation. This is a real but lower-tier priority: the requirement for prior authentication plus user interaction and the niche footprint of baserCMS constrain real-world impact relative to the raw score. Treat it as routine patch-cycle remediation rather than an emergency. |
| Exploit ScenarioDerived | An authenticated baserCMS user with content-entry privileges submits input containing a script payload crafted to bypass the CMS's script validation filter. When another user - such as an administrator or site visitor - views the affected page, the payload executes in their browser, enabling session-context actions like cookie theft or limited data manipulation. No public proof-of-concept is available, and exploitation requires both valid credentials and victim interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 30, 2026
Stored cross-site scripting in baserCMS lets an authenticated user bypass the CMS's script-validation filter and inject arbitrary JavaScript that then executes in the browser of any other user who loads the affected page. The flaw is scored CVSS 3.0 5.4 (medium) with vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, meaning the attacker must already hold a valid baserCMS account with the ability to submit content, and successful execution additionally depends on a second user interacting with the poisoned page. No public exploit code has been identified at time of analysis, and realistic exposure is tempered by the database being reported by JPCERT through Japan's JVN coordination program and by baserCMS's comparatively small deployment base.
RemediationAI
No vendor-released patch or exact fixed version was identified in the available data, so the first step is to consult the JVN advisory at https://jvn.jp/en/jp/JVN14353754 and the vendor notice at https://basercms.net/security/JVN_14353754 for the vendor's patched release and apply it as soon as it is published. Until then, apply compensating controls that target the authenticated-plus-victim-interaction prerequisites of this bug: restrict content authoring, editing, and any other input paths that feed the CMS rendering pipeline to trusted, vetted accounts, since exploitation requires a valid authenticated baserCMS account able to submit content (the trade-off is reduced editorial agility and a need to consolidate authoring privileges); and deploy a Content-Security-Policy that blocks inline and externally sourced script execution on baserCMS-rendered pages, which neutralizes injected script tags at the browser level but can break legitimate themes, plugins, and embedded widgets until the policy is tuned. Also review already-stored content for injected markup and re-sanitize or remove any suspicious entries, because this is a stored XSS and previously persisted payloads will continue to fire after perimeter changes; re-validate stored content after any filter change. Avoid relying on the built-in script-validation filter alone, since its bypass is precisely the defect being remediated.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e. cross-site scripting), specifically a validation-bypass variant: baserCMS applies a script-validation filter to content submitted through its CMS input paths, and that filter can be circumvented so that attacker-supplied markup survives storage and is later rendered into a page served to another user. Because the payload is persisted rather than reflected, this behaves as a stored XSS, which broadens the set of potential victims to anyone who views the affected page. The CVSS vector marks Scope as Changed (S:C), reflecting that the injected script runs in the browser security context of the victim's session rather than staying confined to the vulnerable component, so session cookie theft, authenticated request forgery, or page-content manipulation in the victim's session are the plausible consequences; Confidentiality and Integrity impacts are Low while Availability is None. The supplied CPE, cpe:2.3:a:basercms_user_community:basercms:*:*:*:*:*:*:*:*, uses a wildcard version field, so the available data does not define a specific vulnerable version boundary and all baserCMS releases should be treated as potentially affected until the vendor's advisory at jvn.jp and basercms.net/security/JVN_14353754 specifies otherwise. baserCMS is a PHP-based open source CMS maintained by the baserCMS User Community in Japan, and the report was routed through JPCERT/CC's JVN vulnerability coordination process, which typically accompanies a coordinated vendor fix.
Know when Basercms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
Network-reachable XSS needing a low-privilege authenticated account (PR:L) and victim interaction (UI:R); browser-context execution crosses scope (S:C) with low C/I impact and no availability effect.
Primary rating from Vendor (jpcert).
CVSS VectorVendor: jpcert
Lifecycle Timeline
2DescriptionCVE.org
Cross-Site Scripting via Script Validation Bypass exists in baserCMS. If this vulnerability is exploited, an arbitrary script may be executed in the user's web browser may be caused.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
In baserCMS before 4.1.4, lib\Baser\Model\ThemeConfig.php allows remote attackers to execute arbitrary PHP code via the
SQL injection vulnerability in the baserCMS 3.0.14 and earlier, 4.0.5 and earlier allows remote attackers to execute arb
baserCMS is a website development framework. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploita
baserCMS is a website development framework. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploita
baserCMS is a Content Management system. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
baserCMS is a Content Management system. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
OS command injection in baserCMS installer prior to version 5.2.3 allows remote attackers to execute arbitrary system co
OS command injection in baserCMS update functionality allows authenticated administrators to execute arbitrary commands
OS command injection in baserCMS core update functionality allows authenticated administrators to execute arbitrary syst
baserCMS 3.0.14 and earlier, 4.0.5 and earlier allows an attacker to execute arbitrary PHP code on the server via unspec
Cross-site request forgery (CSRF) vulnerability in baserCMS plugin Mail version 3.0.10 and earlier allows remote attacke
Cross-site request forgery (CSRF) vulnerability in baserCMS plugin Blog version 3.0.10 and earlier allows remote attacke
EUVD-2026-89661
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB