dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-7441

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The StoryChief WordPress plugin has an arbitrary file upload vulnerability in its /wp-json/storychief/webhook REST-API endpoint due to insufficient file type validation. Unauthenticated attackers can upload arbitrary files to the server, potentially achieving remote code execution.

MitigationUpdate the StoryChief plugin to version 1.0.43 or later which contains proper file type validation. If immediate patching is not possible, temporarily disable or restrict access to the affected REST-API endpoint at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify StoryChief plugin is installed
    Navigate to WordPress admin dashboard > Plugins and check if the StoryChief plugin appears in the list of installed plugins
    Affected if StoryChief plugin is present in the plugins list
  2. Check installed StoryChief version
    In WordPress admin > Plugins > StoryChief, click on the plugin name or view the plugin details to see the installed version number
    Affected if Installed version is lower than 1.0.43 (or version cannot be determined and the plugin is present)
  3. Confirm webhook endpoint exposure
    Make a GET request to https://yourdomain.com/wp-json/storychief/webhook (replace yourdomain.com with your actual domain) using curl or a browser. Check if the endpoint responds (even with an error)
    Affected if The endpoint returns any HTTP response (indicating the REST API route is registered and accessible)
  4. Check for unauthorized uploaded files
    Review the wp-content/uploads directory and any custom upload folders configured for StoryChief. Look for file types that do not match expected media (e.g., .php, .phtml, .exe, .js files with suspicious names)
    Affected if Unexpected executable or script files are found in upload directories, especially those with randomized names or created around the time of potential exploitation

You are affected if the StoryChief plugin is installed with a version below 1.0.43 and the /wp-json/storychief/webhook endpoint is accessible, or if suspicious files exist in upload directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the StoryChief plugin to version 1.0.43 or later which contains proper file type validation. If immediate patching is not possible, temporarily disable or restrict access to the affected REST-API endpoint at the web server level.

Recommended fix High confidence

Version 1.0.43 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the StoryChief plugin and check the current version (confirm it is 1.0.42 or below)
  4. Click 'Update Now' if an update is available, or manually update to version 1.0.43 or later
  5. Verify the plugin is updated to version 1.0.43 or higher
  6. Review the /wp-content/uploads/ directory for any unexpected files that may have been uploaded during a potential exploit
  7. Consider running a security scan or malware detection on the site
Caveat Standard security update; test in a staging environment before applying to production if possible

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7441 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7441 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data