CVE-2025-13615
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 StreamTube Core plugin for WordPress is vulnerable to Arbitrary User Password Change in versions up to, and including, 4.78. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for unauthenticated attackers to change user passwords and potentially take over administrator accounts. Note: This can only be exploited if the 'registration password fields' enabled in theme options.
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 StreamTube Core WordPress plugin (versions up to 4.78) contains an authorization bypass vulnerability that allows unauthenticated attackers to change arbitrary user passwords. The plugin fails to properly validate user-controlled objects, enabling attackers to bypass authentication and modify password data for any user account, including administrators. Exploitation requires the 'registration password fields' setting to be enabled in theme options.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify StreamTube Core plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'StreamTube Core' and note the version number displayed.Affected if The plugin is installed and the version is 4.78 or lower (any version up to and including 4.78).
-
Verify the registration password fields setting is enabledAccess the theme options panel (typically found under Appearance > Theme Options or in the theme settings). Locate the 'registration password fields' or similar option controlling password fields during user registration.Affected if The 'registration password fields' setting is currently enabled (turned on).
-
Confirm user registration is accessibleIn WordPress admin, go to Settings > General and verify 'Anyone can register' is checked, or check if there are any active user registration endpoints accessible without authentication.Affected if User registration is enabled or registration endpoints are publicly accessible, allowing unauthenticated access to the vulnerable registration flow.
Your environment is affected if the StreamTube Core plugin (version 4.78 or lower) is installed AND the 'registration password fields' setting is enabled in theme options, allowing unauthenticated password reset exploitation.
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 StreamTube Core plugin to the latest patched version immediately. As a temporary mitigation, disable 'registration password fields' in theme options and consider disabling user registration if not business-critical.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13615 — 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-13615 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