CVE-2025-13680
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 Tiger theme for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 101.2.1. This is due to the plugin allowing a user to update the user role through the $user->set_role() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges to that of an administrator.
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 Tiger WordPress theme has a privilege escalation vulnerability where authenticated users with Subscriber-level access can call the $user->set_role() function to change their own role to Administrator, giving them full site control.
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 Tiger theme installationLog into WordPress admin and go to Appearance > Themes, or inspect /wp-content/themes/tiger/style.css header for the 'Version' commentAffected if Tiger theme is installed and active on the WordPress site
-
Check Tiger theme versionRead the Version field from the theme header in /wp-content/themes/tiger/style.css or from the Themes admin pageAffected if The installed version is 101.2.1 or lower (any version 'up to' 101.2.1)
-
Verify subscriber or low-privileged users existNavigate to Users > All Users in WordPress admin, or query the wp_usermeta table checking for meta_key = 'wp_capabilities' containing 'subscriber' or other non-administrator rolesAffected if Any authenticated user with Subscriber-level access or higher exists on the site
-
Confirm role escalation functionality is presentSearch theme PHP files for occurrences of 'set_role' or '$user->set_role' within /wp-content/themes/tiger/ directory using grep or file searchAffected if The theme contains code that calls set_role() without proper capability checks (e.g., missing 'manage_options' verification)
You are affected if the Tiger theme version is 101.2.1 or below AND your site has any authenticated users with Subscriber-level access or higher who could trigger the vulnerable set_role() 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 Tiger theme to version 101.2.2 or later. If immediate update is not possible, disable user role manipulation functions and audit existing user accounts for unauthorized administrative access.
- Consultation2.0 h
- Implementation2.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13680 — 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-13680 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