dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-5957

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Guest Support – Complete customer support ticket system for WordPress plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'deleteMassTickets' function in all versions up to, and including, 1.2.2. This makes it possible for unauthenticated attackers to delete arbitrary support tickets.

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 confidence

The Guest Support WordPress plugin has a missing capability check on the 'deleteMassTickets' function, allowing unauthenticated attackers to delete arbitrary support tickets via this unprotected function.

MitigationUpdate to a patched version when available; until then, consider disabling the plugin or restricting access at the web server level.

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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Guest Support plugin is installed
    Navigate to WordPress admin > Plugins and locate 'Guest Support' or check the plugin directory /wp-content/plugins/ for a guest-support folder. Note the installed version number from the plugin headers.
    Affected if The plugin is active and installed without a known patched version.
  2. Identify the installed plugin version
    In WordPress admin, click on the Guest Support plugin to view version details, or open the main plugin PHP file (e.g., guest-support.php) and locate the 'Version:' header comment.
    Affected if Version cannot be determined or is older than any patched release.
  3. Verify if deleteMassTickets function is exposed
    Inspect the plugin source code for the 'deleteMassTickets' function. Search for add_action or add_hook calls referencing this function. Check if it is hooked to a public-facing WordPress action/hook without a capability check (e.g., no current_user_can() call before execution).
    Affected if The function exists and is hooked to a public action without permission verification.
  4. Check for evidence of unauthorized ticket deletion
    Review WordPress error logs and any custom logs the plugin may generate. Look for bulk deletion events or ticket removal records that occurred without authenticated admin actions.
    Affected if Ticket deletion events appear in logs without corresponding admin user activity.
  5. Audit WordPress user roles and permissions
    Navigate to Users > Roles or use a role management plugin to verify that no anonymous/unauthenticated users have been granted elevated permissions that could accidentally enable this function.
    Affected if Unauthenticated or subscriber-level users have unexpected capabilities.

If the Guest Support plugin is active and the deleteMassTickets function is accessible without authentication or capability checks, the environment is affected by CVE-2025-5957.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available; until then, consider disabling the plugin or restricting access at the web server level.

Recommended fix High confidence

Guest Support plugin version 1.2.3 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Guest Support' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, manually download the latest version from WordPress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5957 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5957 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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