CVE-2025-2525
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 · uneditedThe Streamit theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'st_Authentication_Controller::edit_profile' function in all versions up to, and including, 4.0.1. This makes it possible for authenticated attackers, with subscriber-level and above permissions, 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 confidenceThe Streamit WordPress theme lacks proper file type validation in the st_Authentication_Controller::edit_profile function, allowing authenticated users with subscriber-level or higher permissions to upload arbitrary files to the server. This arbitrary file upload capability can be leveraged for remote code execution.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Streamit theme installationNavigate to wp-content/themes/ in your WordPress installation and verify the streamit theme directory exists, or check via WordPress admin under Appearance > ThemesAffected if The Streamit theme is installed and active in WordPress
-
Identify Streamit theme versionOpen the style.css file within the streamit theme folder and locate the 'Version:' header line, or check version.php if present in the theme directoryAffected if The theme version has not received the fix for CVE-2025-2525 (compare your version to the latest available from the theme vendor)
-
Verify edit_profile capability assignmentInspect the st_Authentication_Controller class in the theme code to determine which user roles are permitted to access the edit_profile function; alternatively, check WordPress user role capabilities for subscriber-level accountsAffected if Subscriber-level or higher roles have access to the edit_profile function without additional capability checks
-
Audit uploaded files in media directoryReview files in wp-content/uploads/ and its subdirectories for unexpected file extensions such as .php, .php5, .phtml, .exe, or .js that were not intentionally uploaded by administratorsAffected if Arbitrary or executable file types exist in the uploads directory that were not explicitly allowed by the site administrator
Your environment is affected if the Streamit theme is installed, the installed version is unpatched, and subscriber-level authenticated users can access the edit_profile upload function.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the Streamit theme to version 4.0.2 or later, which should include proper file type validation. Until then, restrict file upload capabilities or disable the affected profile editing functionality.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2525 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2525 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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