CVE-2026-115565 json
storyblok-backup: Stored path traversal via unsanitized Storyblok component names in backup output
published 2mo ago modified yesterday also EUVD-2026-130526 , GHSA-vcx7-pfrh-mcfg
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 30%
- public exploits
- 0
- none known
Summary
storyblok-backup is an npx CLI tool to create backups of a Storyblok space and restore individual resources. Prior to 0.7.1, the writeJson function used the editable Storyblok component name field as a filename without path containment. A person with component-management access in a Storyblok space could store a component name containing path traversal sequences; when another user later ran a backup for that space, the stored name escaped the configured backup directory and caused a JSON file to be written outside it on the backup host. Depending on the path chosen and the backup process's permissions, this could overwrite existing files at attacker-chosen locations. The vulnerability is specific to components: stories and datasources use numeric identifiers, and asset names are reduced to a final path segment. This issue is fixed in version 0.7.1.
Patch / fix
- npm storyblok-backup 0.7.1
Is CVE-2026-115565 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2d ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-21).
Exploits and checks
- github.com https://github.com/webflorist/storyblok-backup/security/advisories/GHSA-vcx7-pfrh-mcfg referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 5.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | storyblok-backup | <0.7.1 |
0.7.1 |
Affected products
- webflorist storyblok-backup
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/webflorist/storyblok-backup/commit/f4e4bb1979832abd7e4eb1666e2b3cfc767f587a
web
-
github.com
/webflorist/storyblok-backup/security/advisories/GHSA-vcx7-pfrh-mcfg
exploit, web, advisory
-
github.com
/webflorist/storyblok-backup/releases/tag/v0.7.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-115565
advisory
-
github.com
/webflorist/storyblok-backup
package
Sources
- CVE List CVE-2026-115565
- GitHub Advisory GHSA-vcx7-pfrh-mcfg
- NVD CVE-2026-115565
- Maintainer advisory GHSA-vcx7-pfrh-mcfg
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of webflorist/storyblok-backup published their own advisory on GitHub. Reviewed sources take precedence over it.