dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25311

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-19
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 10up Autoshare for Twitter autoshare-for-twitter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Autoshare for Twitter: from n/a through <= 2.3.1.

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

The 10up Autoshare for Twitter plugin <= 2.3.1 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This means the plugin fails to properly verify user permissions before allowing certain actions, potentially permitting unauthorized users to trigger Twitter autoshare functionality.

MitigationUpdate to the latest version of Autoshare for Twitter when available. In the meantime, restrict user access to only trusted, authorized personnel and implement proper capability checks on all plugin actions that modify post settings.

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 the plugin installation
    Check the wp-content/plugins/ directory for a folder named 'autoshare-for-twitter' or similar 10up Twitter autoshare plugin folder
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Determine the installed version
    Open the main plugin PHP file (usually autoshare-for-twitter.php) and check the version header comment (e.g., 'Version: x.x.x') or check the plugin version via WordPress admin plugins page
    Affected if The reported version is 2.3.1 or lower
  3. Verify autoshare functionality is active
    Check if the plugin is activated in WordPress admin under Plugins > Installed Plugins, and inspect post edit screens or plugin settings to see if Twitter autoshare options are enabled for posts
    Affected if The plugin is active and autoshare features are configured on posts or settings
  4. Inspect user access controls
    Review WordPress user roles and capabilities assigned to users who can edit posts. Check which roles have permission to modify autoshare settings (typically found in plugin settings or post meta boxes)
    Affected if Users without administrator-level permissions can access or modify autoshare settings

You are affected if the Autoshare for Twitter plugin is installed at version 2.3.1 or lower and users with limited roles can access autoshare functionality without proper permission 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 to the latest version of Autoshare for Twitter when available. In the meantime, restrict user access to only trusted, authorized personnel and implement proper capability checks on all plugin actions that modify post settings.

Recommended fix Moderate confidence

Latest version newer than 2.3.1 (check WordPress plugin repository for current release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Autoshare for Twitter' plugin (10up)
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, manually download the latest version from the WordPress plugin repository or 10up's official repository
  6. 6. Deactivate and delete the old version if automatic update doesn't work, then install the new version
  7. 7. After updating, verify the plugin functionality and test that authorization controls are working properly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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