Unauthorized role changes via updateRoles
Published Jan 10, 2024 · Updated Jun 3, 2025
Improper access control in Mandelo ssm_shiro_blog 1.0 allows remote attackers to modify Backend role assignments via updateRoles. Public records identify updateRoles as the affected locus but do not disclose the missing authorization check or its parameter handling. Published assessments require no credentials or user interaction and limit the reported consequence to unauthorized integrity changes.
Summary
What happened
Improper access control in Mandelo ssm_shiro_blog 1.0 allows remote attackers to modify Backend role assignments via updateRoles. Public records identify updateRoles as the affected locus but do not disclose the missing authorization check or its parameter handling. Published assessments require no credentials or user interaction and limit the reported consequence to unauthorized integrity changes.
The record
- CVE
- CVE-2024-0356
- Published
- Jan 10, 2024
- Updated
- Jun 3, 2025
- Vendor
- Mandelo
- Product
- ssm_shiro_blog
- Classifications
- CWE-284, T1098
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- ssm has a vertical override vulnerabilityproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo