CVE-2025-13675
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 'paypal-submit.php' file not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site.
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 in paypal-submit.php where user role registration is not restricted. Unauthenticated attackers can specify the 'administrator' role during registration to gain full administrative access to the WordPress site.
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.
-
Locate the Tiger theme installationCheck the wp-content/themes/ directory for a folder named 'tiger' or similar (theme folder names vary). Common path: /wp-content/themes/tiger/Affected if The Tiger theme folder exists in the WordPress themes directory
-
Determine the installed Tiger theme versionOpen the theme's style.css file (usually at wp-content/themes/tiger/style.css) and look for the 'Version:' header in the CSS comment block at the topAffected if The version listed is below 101.2.2 (e.g., 101.2.1, 101.2.0, etc.)
-
Check if the vulnerable paypal-submit.php existsLook for the file paypal-submit.php inside the Tiger theme folder (e.g., wp-content/themes/tiger/paypal-submit.php)Affected if The file paypal-submit.php exists in the theme directory
-
Verify the vulnerability conditionIf the version is below 101.2.2 AND paypal-submit.php exists, the environment is vulnerable to unauthenticated privilege escalationAffected if Both conditions are true: version < 101.2.2 AND paypal-submit.php is present
You are affected if the Tiger WordPress theme version is below 101.2.2 and the paypal-submit.php file exists in the theme directory, allowing unauthenticated users to register with administrator privileges.
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 an update is unavailable, remove the vulnerable paypal-submit.php file and audit existing administrator accounts for unauthorized access.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13675 — 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-13675 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