Security readout for executives and security teams
Plain-English summary
Joruri CMS 2017 Release2 and earlier has a cross-site scripting issue. An attacker could inject script or HTML through unspecified vectors, potentially affecting people who view the vulnerable page. The provided sources do not include CVSS scoring, detailed vectors, or confirmed exploitation.
Executive priority
Prioritize this if Joruri CMS supports public services, citizen portals, or authenticated user workflows. The limited technical detail lowers confidence, but XSS in a CMS can affect trust, sessions, and user safety.
Technical view
CVE-2019-5967 is an XSS vulnerability in SiteBridge Joruri CMS 2017 Release2 and earlier. The CVE description states remote attackers can inject arbitrary web script or HTML, but the source bundle does not specify reflected versus stored XSS, parameters, authentication requirements, or affected routes.
Likely exposure
Exposure is likely limited to organizations running Joruri CMS 2017 Release2 or earlier, especially internet-facing deployments. The exact vulnerable entry points are not specified in the provided evidence.
Exploitation context
The CVE is not listed as KEV in the bundle, and no cited source confirms active exploitation. Public details are sparse, so treat exploitability as plausible but unconfirmed.
Researcher notes
The key gap is vector detail: no parameter, route, privilege requirement, or XSS type is provided in the bundle. Avoid assuming exploitability beyond remote script or HTML injection until vendor/JVN details are reviewed.
Mitigation direction
- Identify any Joruri CMS 2017 installations and exact release levels.
- If Release2 or earlier is present, review SiteBridge and JVN guidance.
- Plan upgrade, replacement, or compensating controls based on vendor instructions.
- Restrict access to administrative CMS functions where possible.
- Monitor CMS pages and logs for suspicious script injection indicators.
Validation and detection
- Inventory public and internal sites using Joruri CMS.
- Confirm whether any instance is Joruri CMS 2017 Release2 or earlier.
- Review vendor and JVN advisories for affected component details.
- Check web logs for unusual HTML or script-like input patterns.
- Verify remediation against vendor guidance after changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-5967 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://joruri.org/docs/2018060400058/CVE reference · x_refsource_MISC
- https://jvn.jp/en/jp/JVN29188908/index.htmlCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.