dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-53345

HIGH · 8.8 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Missing Authorization vulnerability leading to code execution after installing malicious vulnerable plugin in ThimPress Thim Core. This issue affects Thim Core: from n/a through 2.3.3.

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

Missing authorization check in Thim Core allows unauthenticated or lower-privileged users to install and activate arbitrary plugins via the plugin installation functionality, leading to remote code execution.

MitigationUpgrade Thim Core to version 2.3.4 or later which includes proper authorization checks, or implement capability checks and nonce validation on plugin installation/activation endpoints.

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
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. Identify if Thim Core is installed
    Check your WordPress theme directory for the Thim Core framework. Common paths include wp-content/themes/*/thim-core/ or look for the Thim Core plugin if distributed as a separate plugin. Check theme or plugin header for version information.
    Affected if Thim Core is present and the version is within the affected range (if known)
  2. Determine Thim Core version
    Locate the main Thim Core file (often thim-core.php or class-thim-core.php) and read the Version header from the file comments, or check the plugin/theme metadata via WordPress admin under Plugins or Appearance > Themes.
    Affected if The installed version matches or falls within the vulnerable version range for CVE-2025-53345
  3. Verify user role and capability configuration
    In WordPress admin, go to Users > All Users and review which roles have the 'install_plugins' or 'activate_plugins' capabilities. Check if any custom roles or low-privilege users (such as Subscribers or Contributors) have been granted plugin management capabilities.
    Affected if Users without administrator-level permissions have plugin installation or activation capabilities
  4. Inspect plugin management access controls
    If you have code access, examine the thim-core plugin installation/activation handlers. Look for function calls related to plugin installation (such as plugins_api, wp_install_plugin, or AJAX handlers for 'install-plugin' and 'activate-plugin') and verify they include current_user_can() or similar authorization checks.
    Affected if Plugin installation or activation functions lack proper capability checks (e.g., no current_user_can('install_plugins') before execution)
  5. Test plugin installation endpoint exposure
    Use a low-privilege test account (e.g., Subscriber role) to attempt accessing the plugin installation functionality via wp-admin or AJAX endpoints. Observe if the request is rejected or allowed.
    Affected if A non-administrator user can access or trigger plugin installation/activation without proper authorization

You are affected if Thim Core is installed and the plugin management functionality permits users without proper administrative capabilities to install or activate plugins, allowing arbitrary code execution.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Thim Core to version 2.3.4 or later which includes proper authorization checks, or implement capability checks and nonce validation on plugin installation/activation endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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