Cyber Resilience

CVE-2023-41889

Ss-Proj Shirasagi ≤ 1.18.0

Public PoC
Published
15 September 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0058 45th percentile
Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2023-41889 is a medium-severity Improper Handling of Unicode Encoding (CWE-176) vulnerability in Ss-Proj Shirasagi. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

SHIRASAGI is a Content Management System. Prior to version 1.18.0, SHIRASAGI is vulnerable to a Post-Unicode normalization issue. This happens when a logical validation or a security check is performed before a Unicode normalization. The Unicode character equivalent of a…

more

character would resurface after the normalization. The fix is initially performing the Unicode normalization and then strip for all whitespaces and then checking for a blank string. This issue has been fixed in version 1.18.0.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1027.018 Invisible Unicode Stealth
Adversaries may abuse invisible or non-printing Unicode characters to conceal malicious content within files, scripts, or text.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1027 Obfuscated Files or Information Stealth
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit.
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1132 Data Encoding Command And Control
Adversaries may encode data to make the content of command and control traffic more difficult to detect.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-22425Same product: Ss-Proj Shirasagi
CVE-2023-38569Same product: Ss-Proj Shirasagi
CVE-2023-36492Same product: Ss-Proj Shirasagi
CVE-2023-22427Same product: Ss-Proj Shirasagi
CVE-2023-39448Same product: Ss-Proj Shirasagi
CVE-2024-46898Same product: Ss-Proj Shirasagi
CVE-2026-35373Shared CWE-176
CVE-2024-8067Shared CWE-176
CVE-2026-35346Shared CWE-176
CVE-2025-55129Shared CWE-176

Affected Assets

ss-proj
shirasagi
≤ 1.18.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.2.1
  • V1.2.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-116

Validating that output matches expected content directly mitigates failures to properly encode or escape data for its destination context.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper Unicode/input validation to prevent this weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards explicitly require correct output encoding and escaping to preserve message structure.

finds

Security testing can detect Unicode-handling flaws before deployment.

prevents

Secure development lifecycle mandates input validation and encoding handling that can prevent Unicode mishandling.

prevents

Application security requirements include proper handling of character encodings and input sanitization.

prevents

Secure architecture principles require robust input processing to avoid encoding-related vulnerabilities.

References