CVE-2025-49422
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 · uneditedIncorrect Privilege Assignment vulnerability in themepassion Support Ticket support-ticket allows Privilege Escalation.This issue affects Support Ticket: from n/a through <= 1.9.
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 · moderate confidenceAn incorrect privilege assignment vulnerability in the themepassion Support Ticket plugin (versions <=1.9) allows attackers to escalate privileges, likely enabling unauthenticated or low-privileged users to gain administrative access to the system.
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.
-
Check Support Ticket plugin version in WordPressNavigate to Plugins > Installed Plugins in the WordPress admin dashboard. Locate the 'Support Ticket' (or 'themepassion Support Ticket') plugin and read the version number displayed beneath the plugin name. Alternatively, access the site via FTP or file manager and locate the plugin directory (typically /wp-content/plugins/support-ticket/ or similar), then open the main plugin PHP file and check the 'Version' header in the plugin comments.Affected if The installed version is 1.9 or lower (1.9, 1.8, 1.7, etc.)
-
Audit WordPress user accounts for unauthorized admin accessNavigate to Users > All Users in the WordPress admin dashboard. Review the list of users and their assigned roles. Look for accounts with the 'Administrator' role that you do not recognize, or that were created recently without your knowledge.Affected if There are administrator accounts that were created without authorization or by unexpected users, indicating the privilege escalation may have been exploited
-
Review recent user role changesIf your WordPress installation has activity logging enabled (via plugins like Activity Log or WP Security Audit Log), review the logs for any recent changes to user roles, particularly promotions to Administrator. Check the user creation date and login history for suspicious activity.Affected if User role changes to Administrator occurred without legitimate admin action, or new admin accounts were created by low-privileged users
You are affected if the themepassion Support Ticket plugin version is 1.9 or lower AND you discover unauthorized administrator accounts or unexpected privilege escalations in your WordPress users.
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 dataUpgrade the Support Ticket plugin to a version beyond 1.9 once available, or disable the plugin until a patch is released; audit user accounts and privilege assignments for unauthorized administrative access.
- 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-49422 — 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-49422 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