dbcve.org
Game Users Share ButtonWordPress extension · Gameusers

CVE-2025-6755

HIGH · 8.8 CVSS v3.1 Published 2025-06-28
Fix available
A fix is available. Upgrade to after 1.3.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Game Users Share Buttons plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the ajaxDeleteTheme() function in all versions up to, and including, 1.3.0. This makes it possible for Subscriber-level attackers to add arbitrary file paths (such as ../../../../wp-config.php) to the themeNameId parameter of the AJAX request, which can lead to remote code execution.

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 Game Users Share Buttons WordPress plugin versions up to 1.3.0 contain an arbitrary file deletion vulnerability in the ajaxDeleteTheme() function. Due to insufficient path validation on the themeNameId parameter, authenticated Subscriber-level users can traverse directories (e.g., ../../../../wp-config.php) to delete critical files, potentially leading to remote code execution.

MitigationImmediately update the plugin to a patched version; if unavailable, deactivate the plugin. Restrict or disable the ajaxDeleteTheme() AJAX endpoint until patched, and audit for any signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Game Users Share ButtonWordPress extension
Affected:<= 1.3.0

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 checks

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

  1. Verify the plugin is installed
    Check your WordPress plugins directory for the 'gameusers-share-buttons' folder, or query the wp_options table for the active_plugins entry
    Affected if The plugin 'gameusers-share-buttons' is present in the plugins list
  2. Identify the installed version
    Open the main plugin file (usually gameusers-share-buttons.php) and locate the Version header in the plugin comment block, or check the wp_options table for the option_name containing 'gameusers'
    Affected if The version number is 1.3.0 or lower
  3. Confirm the vulnerable AJAX endpoint is accessible
    Check if the file containing ajaxDeleteTheme() function exists in the plugin directory (typically includes/ajax.php or similar), and test if the wp_ajax_gameusers_delete_theme or wp_ajax_nopriv hook is registered
    Affected if The ajaxDeleteTheme() function is present and the AJAX endpoint is registered
  4. Verify subscriber-level user accounts exist
    Query the wp_usermeta table for users with wp_capability meta_value showing 'subscriber' role, or check Users > All Users in WordPress admin for subscriber accounts
    Affected if At least one user with Subscriber role exists in the system
  5. Check for recent file deletion activity
    Review web server access logs for POST requests to the ajaxDeleteTheme endpoint with unusual themeNameId parameters (containing ../), and check if critical files like wp-config.php are missing or modified
    Affected if Log entries show requests to the delete function with path traversal patterns, or critical files have been recently deleted

You are affected if the Game Users Share Buttons plugin version is 1.3.0 or lower, the ajaxDeleteTheme() function is present and accessible, and any subscriber-level users exist in your WordPress installation.

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
Upgrade available Upgrade to a release after 1.3.0
Interim mitigation

Immediately update the plugin to a patched version; if unavailable, deactivate the plugin. Restrict or disable the ajaxDeleteTheme() AJAX endpoint until patched, and audit for any signs of exploitation.

Recommended fix Low confidence
  1. Check wordpress.org for the latest version of the Game Users Share Button plugin to confirm if a security update has been released.
  2. If a newer version exists, upgrade to that version immediately.
  3. If no patched version is available, consider the following mitigations:
  4. 1. Disable the Game Users Share Button plugin until a security update is available
  5. 2. Restrict user registration on the WordPress site to prevent subscriber-level accounts from being created
  6. 3. Review user roles and permissions - ensure no untrusted users have subscriber-level access
  7. 4. Implement file system permissions to prevent modification of critical files like wp-config.php
  8. 5. Consider using a Web Application Firewall (WAF) to block path traversal attempts

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

Fix this in Game Users Share Button Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6755 — 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-6755 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