dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66110

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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
Missing Authorization vulnerability in bPlugins Tiktok Feed b-tiktok-feed allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Tiktok Feed: from n/a through <= 1.0.23.

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 vulnerability in the bPlugins Tiktok Feed WordPress plugin (b-tiktok-feed <= 1.0.23) allows unauthenticated or unauthorized users to access functionality that should be protected by access controls. The plugin fails to properly validate user permissions before executing certain actions.

MitigationUpdate the Tiktok Feed plugin to the latest version that includes proper authorization checks, or implement role-based access control (RBAC) checks on all sensitive endpoints within the plugin.

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. Locate the b-tiktok-feed plugin installation
    Check the wp-content/plugins/ directory for a folder named b-tiktok-feed or similar TikTok-related plugin from bPlugins. Also check via WordPress admin under Plugins > Installed Plugins.
    Affected if The b-tiktok-feed plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Open the main plugin file (usually b-tiktok-feed.php) and look for the 'Version:' header in the plugin comment block, or check the readme.txt file for the version number.
    Affected if The version number is 1.0.23 or lower, or if the version cannot be determined (indicating an older installation)
  3. Inspect plugin PHP files for authorization logic
    Examine the main plugin PHP files for function calls that handle user capabilities, such as current_user_can(), check_admin_referer(), or nonce verification. Look for AJAX handlers or form processing functions.
    Affected if No capability checks (current_user_can) or insufficient permission validation is found before sensitive operations
  4. Test access to plugin endpoints without authentication
    If the plugin exposes AJAX actions (check wp_ajax_ and wp_ajax_nopriv_ hooks in the code), attempt to access these endpoints without logging in to see if they execute without requiring authorization.
    Affected if Plugin endpoints respond to unauthenticated requests and perform actions without verifying user permissions

A user is affected if the b-tiktok-feed plugin version is 1.0.23 or lower AND the plugin exposes functionality that can be accessed or triggered without proper authorization checks.

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 the Tiktok Feed plugin to the latest version that includes proper authorization checks, or implement role-based access control (RBAC) checks on all sensitive endpoints within the plugin.

Recommended fix Moderate confidence

Version 1.0.24 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate the 'Tiktok Feed' (b-tiktok-feed) plugin in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or bPlugins website
  6. 6. Deactivate and delete the old version if auto-update does not work, then upload and activate the new version
  7. 7. Verify the plugin is functioning correctly after the update
  8. 8. Test that the authorization controls are properly enforced
Caveat Review plugin settings after upgrade as configuration may need re-verification

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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-66110 — 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-66110 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