dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2026-6446

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-02
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
The My Social Feeds – Social Feeds Embedder plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to and including 1.0.4 via the 'ttp_get_accounts' AJAX action. This is due to the complete absence of authorization checks (no capability verification) and nonce verification in the get_accounts() function, which returns the full contents of the 'ttp_tiktok_accounts' WordPress option. This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive TikTok OAuth credentials, including access_token and refresh_token values, that belong to administrator-connected TikTok accounts, enabling them to impersonate the site owner when interacting with the TikTok API.

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 WordPress plugin 'My Social Feeds – Social Feeds Embedder' versions up to 1.0.4 contains a missing authorization vulnerability in the ttp_get_accounts AJAX action. The get_accounts() function lacks both capability verification and nonce validation, allowing any authenticated user with Subscriber-level access or higher to retrieve the complete ttp_tiktok_accounts option contents, including OAuth access_token and refresh_token values belonging to administrator-connected TikTok accounts.

MitigationImplement proper authorization checks using WordPress capability verification (e.g., manage_options) and nonce validation in the get_accounts() function to ensure only authorized administrators can access sensitive OAuth credentials.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'My Social Feeds - Social Feeds Embedder' or check the plugins directory for the plugin folder name (typically my-social-feeds or similar)
    Affected if The plugin is installed and active
  2. Check the installed version
    In WordPress admin, go to Plugins > Installed Plugins and view the version number listed under the plugin name 'My Social Feeds - Social Feeds Embedder'; alternatively check the main plugin file header for the Version field
    Affected if Version is 1.0.4 or lower
  3. Verify the vulnerable AJAX action exists
    Examine the main plugin PHP file for the register AJAX action registration: add_action('wp_ajax_ttp_get_accounts', 'get_accounts'); or wp_ajax_nopriv_ttp_get_accounts
    Affected if The ttp_get_accounts AJAX action is registered without capability checks
  4. Inspect the get_accounts function for authorization
    Locate the get_accounts() function in the plugin files and verify if it contains current_user_can() or a capability check, and if it performs nonce verification using wp_verify_nonce or check_ajax_referer
    Affected if The function lacks both capability verification (e.g., current_user_can('manage_options')) and nonce validation
  5. Check for sensitive TikTok OAuth data
    In WordPress database, query the wp_options table for the option_name 'ttp_tiktok_accounts' and examine if it contains access_token and refresh_token values
    Affected if The ttp_tiktok_accounts option exists and contains OAuth credentials

A user is affected if the plugin version is 1.0.4 or lower, the ttp_get_accounts AJAX action is present without authorization checks, and the ttp_tiktok_accounts option contains OAuth tokens that any authenticated subscriber-level user could potentially retrieve.

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

Implement proper authorization checks using WordPress capability verification (e.g., manage_options) and nonce validation in the get_accounts() function to ensure only authorized administrators can access sensitive OAuth credentials.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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