Storyden through 1.26.16 Privilege Escalation via MANAGE_ROLES Role Assignment
Only affects Storyden through v1.26.16, where a custom role holding only MANAGE_ROLES can grant the built-in Admin role. No vendor rating is given and no fix is listed in the facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Storyden through release v1.26.16, confirmed on the main branch at a specific commit The attacker's account holds a custom role with the MANAGE_ROLES permission and without ADMINISTRATOR
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Storyden, through version 1.26.16, lets users who hold the MANAGE_ROLES permission grant themselves or others the ADMINISTRATOR permission without being administrators, which allows full takeover of the instance. An attacker reaches it remotely over the network, but must first log in with a account holding MANAGE_ROLES (high privileges required).
Read the original description
Storyden through 1.26.16 contains a privilege escalation vulnerability that allows users holding MANAGE_ROLES to grant the ADMINISTRATOR permission without being administrators. Attackers can call AccountAddRole on another controlled account or use RoleCreate and RoleUpdate to create administrator roles, taking full control of the instance.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects Storyden through release v1.26.16, confirmed on the main branch at a specific commit The attacker's account holds a custom role with the MANAGE_ROLES permission and without ADMINISTRATORApply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Southclaws storyden
through 1.26.16
Evidence 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125360
Is CVE-2026-125360 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A user who holds a custom role with the MANAGE_ROLES permission, but not ADMINISTRATOR, can assign the built-in Admin role to accounts they control. That gives them full control of the instance, including deleting content, managing all accounts, and changing instance-wide settings.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-125360?
storyden: through 1.26.16.Source: cve.now feed data
Am I affected, and how do I check?
The affected range runs from the start of the product's history through release v1.26.16, and the issue was confirmed on the main branch at commit 609e4db12b8a0cd7f44287957c0a709b56a265e2. To check a setup, look at whether any custom role has the MANAGE_ROLES permission without ADMINISTRATOR, and compare your installed version against v1.26.16.Source: github.com, vulncheck.com
How do I fix CVE-2026-125360?
The facts do not name a fixed release, so no upgrade target can be given from them. Check the project's release notes for a version later than v1.26.16 that addresses this issue.Source: github.com, vulncheck.com