CVE-2025-7441 in the critical feed json
StoryChief <= 1.0.42 - Unauthenticated Arbitrary File Upload
published last yr. modified 4mo ago also EUVD-2025-25062
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 50.9%
- EPSS 50.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 2
- Metasploit and Exploit-DB
Summary
The StoryChief plugin for WordPress is vulnerable to arbitrary file uploads in all versions up to, and including, 1.0.42. This vulnerability occurs through the /wp-json/storychief/webhook REST-API endpoint that does not have sufficient filetype validation. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible.
Is CVE-2025-7441 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (Metasploit exploit/multi/http/wp_plugin_story_chef_file_upload)
- Published
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
50.88% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/multi/http/wp_plugin_story_chef_file_upload WordPress StoryChief Plugin Unauthenticated RCE metasploit exploit, excellent rank, 2025-08-04
- EDB-52422 StoryChief Wordpress Plugin 1.0.42 - Arbitrary File Upload webapps, 2025-08-26
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- storychief StoryChief
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
- Technology feeds
References
Sources
- CVE List CVE-2025-7441
- NVD CVE-2025-7441
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.