CVE-2025-2526
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 privilege escalation via account takeover in all versions up to, and including, 4.0.2. This is due to the plugin not properly validating a user's identity prior to updating their details like email in the 'st_Authentication_Controller::edit_profile' function. This makes it possible for unauthenticated attackers to change arbitrary user's email addresses, including administrators, and leverage that to reset the user's password and gain access to their account.
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 (versions up to 4.0.2) contains an unauthenticated privilege escalation vulnerability in the st_Authentication_Controller::edit_profile function. The function fails to validate the user's identity before allowing email address changes, enabling any unauthenticated attacker to modify arbitrary user emails (including administrators) and subsequently reset passwords to hijack accounts.
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.
-
Identify Streamit theme installation and versionIn WordPress admin, go to Appearance > Themes to confirm Streamit is active. Check the theme's style.css file or theme header for the version number. Alternatively, examine the theme's main directory files for a version constant or readme.txt.Affected if Streamit theme version is 4.0.2 or earlier
-
Locate the vulnerable authentication controller fileSearch the wp-content/themes/streamit directory for a file containing 'st_Authentication_Controller' class definition, typically in a file named something like class-st-authentication-controller.php or within authentication-related PHP files in the theme's includes or controllers folder.Affected if The file exists and contains the edit_profile function without proper user identity validation
-
Audit user accounts for unauthorized email modificationsQuery the wp_usermeta table for recent changes to the 'billing_email' or 'user_email' meta keys. Check WordPress user admin panel for any accounts with email addresses that were changed without corresponding user action logs.Affected if Any administrator or high-privilege user accounts have email addresses changed without authorized request, or email changes occurred from unauthenticated sources
-
Review server access logs for profile update requestsExamine HTTP access logs for POST requests to endpoints that trigger the edit_profile function (search for patterns like '/profile', '/edit-profile', '/authentication/edit_profile', or theme-specific AJAX endpoints handling user profile updates.Affected if Requests to profile update endpoints originate from unauthenticated IP addresses or show evidence of mass enumeration of user IDs
-
Check for unexpected password reset activityReview WordPress security logs and email server logs for password reset requests targeting administrator accounts that were initiated without prior legitimate password reset request by the account owner.Affected if Password reset emails were sent for admin accounts without corresponding user-initiated reset requests
A user is affected if Streamit theme version 4.0.2 or earlier is installed and unauthenticated requests can modify user email addresses or trigger password resets.
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 Streamit theme to version 4.0.3 or later which includes proper identity validation. Until patched, monitor user accounts for unauthorized email changes and consider restricting profile update endpoints via WAF rules.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2526 — 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-2526 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