dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-60096

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in CodexThemes TheGem (Elementor) thegem-elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects TheGem (Elementor): from n/a through <= 5.10.5.

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 confidence

A missing authorization vulnerability in TheGem (Elementor) plugin versions up to 5.10.5 allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to privileged functions or data.

MitigationImplement proper authorization checks on all sensitive endpoints and functions within the plugin; update to the latest patched version when available.

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

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

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. Locate TheGem plugin version in WordPress
    In WordPress admin, go to Plugins > Installed Plugins > TheGem. The version number is displayed below the plugin name. Alternatively, check the main plugin file (typically thegem.php in wp-content/plugins/thegem) for the 'Version' header in the file comment block.
    Affected if The installed version is 5.10.5 or lower
  2. Confirm version against affected range
    Compare your installed version number to 5.10.5. Any version up to and including 5.10.5 is within the affected range.
    Affected if Version is 5.10.5 or any earlier version number
  3. Identify accessible sensitive endpoints
    Check if your site exposes any TheGem-related AJAX endpoints or admin-privileged functions publicly. Common locations include wp-admin/admin-ajax.php calls with 'thegem' action parameters, or custom API endpoints. Inspect network traffic and source code for any thegem_ prefixed functions that may execute without capability checks.
    Affected if Sensitive endpoints or functions are accessible without authentication or proper authorization checks

You are affected if TheGem plugin version is 5.10.5 or lower AND your environment exposes privileged functions or endpoints without proper authorization controls.

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

Implement proper authorization checks on all sensitive endpoints and functions within the plugin; update to the latest patched version when available.

Recommended fix Moderate confidence

Version newer than 5.10.5 (verify release notes for CVE-2025-60096 fix)

  1. 1. Identify the currently installed version of TheGem theme in your WordPress installation.
  2. 2. Check TheGem theme's official release notes or CodexThemes repository for versions newer than 5.10.5 that address security fixes.
  3. 3. Before upgrading, create a complete backup of your WordPress site including database and files.
  4. 4. Test the upgrade in a staging environment first to ensure compatibility with your current WordPress version and active plugins.
  5. 5. If a newer version is available (verify it includes CVE-2025-60096 fix), upgrade to that version through WordPress admin or by uploading the new theme package.
  6. 6. After upgrade, verify that thegem-elementor access controls are functioning correctly.
  7. 7. Review user roles and permissions for any unauthorized access that may have occurred.
Caveat Theme updates may affect custom styling or child theme configurations; test thoroughly before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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