dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-2519

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Sreamit theme for WordPress is vulnerable to arbitrary file downloads in all versions up to, and including, 4.0.1. This is due to insufficient file validation in the 'st_send_download_file' function. This makes it possible for authenticated attackers, with subscriber-level access and above, to download arbitrary files.

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 Streamit WordPress theme contains an arbitrary file download vulnerability in the 'st_send_download_file' function due to insufficient file validation. Authenticated attackers with subscriber-level access or higher can exploit this to download arbitrary files from the server filesystem, potentially exposing sensitive system files, credentials, or configuration data.

MitigationUpdate the Streamit theme to version 4.0.2 or later once available. Until a patch is released, restrict or disable the affected functionality and monitor for unauthorized access attempts.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm Streamit theme is installed
    Navigate to Appearance > Themes in the WordPress admin dashboard and verify the Streamit theme is active. The theme files are typically located in /wp-content/themes/streamit/
    Affected if The Streamit theme is installed and active on the WordPress site
  2. Check installed Streamit theme version
    In the WordPress admin, go to Appearance > Themes and click on the Streamit theme to view its details. Alternatively, inspect the style.css file in /wp-content/themes/streamit/ and look for the 'Version:' header in the theme comments
    Affected if The installed version is lower than the patched version 4.0.2 (compare your version to determine if it is below this release)
  3. Verify vulnerable function exists
    Check if the file containing the st_send_download_file function exists in the theme. Look for PHP files in /wp-content/themes/streamit/ that may contain this function, particularly in includes or functions directories
    Affected if The st_send_download_file function is present in the theme code
  4. Confirm WordPress user registration is enabled
    In the WordPress admin, go to Settings > General and check if the 'Anyone can register' option is enabled. Also verify which default user role is assigned (subscriber, contributor, etc.)
    Affected if User registration is open or subscriber-level accounts can be created
  5. Test if download endpoint is accessible
    Attempt to access the download functionality endpoint (typically via a URL parameter referencing the st_send_download_file function). Check for common patterns like ?action=st_send_download_file or similar in the theme's AJAX or public-facing files
    Affected if The download function endpoint is publicly accessible without additional access controls

The site is affected if Streamit theme is installed with a version below 4.0.2, the vulnerable function exists, and subscriber-level users can access the download functionality.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Streamit theme to version 4.0.2 or later once available. Until a patch is released, restrict or disable the affected functionality and monitor for unauthorized access attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,870
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2519 — 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-2519 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