dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57731

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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
Contributor Broken Access Control in Flatsome <= 3.20.5 versions.

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

This is a Broken Access Control vulnerability in the Flatsome WordPress theme (versions 3.20.5 and below) that allows users with the Contributor role to perform unauthorized actions they should not have access to. The specific privileges or actions that can be exploited are not detailed in the available description.

MitigationUpdate Flatsome theme to the latest version (above 3.20.5) to remediate this vulnerability. As a WordPress theme update, this should be tested thoroughly after implementation to ensure compatibility with existing site functionality and child themes.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check Flatsome theme version
    Navigate to Appearance > Themes in WordPress admin panel and locate Flatsome. The version is displayed in the theme details. Alternatively, open wp-content/themes/flatsome/style.css and read the Version: header
    Affected if Version is 3.20.5 or lower
  2. Identify Contributor role users
    In WordPress admin, go to Users > All Users and filter by Contributor role. Alternatively, query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'contributor'
    Affected if Any users with Contributor role exist on the site
  3. Verify Contributor role permissions
    As an administrator, review the Contributor role capabilities using a role management plugin or via wp_roles() function. Test whether Contributors can access features beyond their intended scope such as publishing content, accessing theme options, or modifying settings
    Affected if Contributors can perform actions they should not have permission to perform

If Flatsome version is 3.20.5 or below AND Contributor role users exist on the site, the environment is likely affected by this Broken Access Control vulnerability

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 Flatsome theme to the latest version (above 3.20.5) to remediate this vulnerability. As a WordPress theme update, this should be tested thoroughly after implementation to ensure compatibility with existing site functionality and child themes.

Recommended fix Moderate confidence

Upgrade to Flatsome version 3.20.6 or later (verify latest version at uxthemes.com)

  1. 1. Log into your WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Flatsome theme and check the current version number
  4. 4. Visit the official Flatsome theme page (uxthemes.com) or WordPress theme repository to verify the latest available version
  5. 5. If a version newer than 3.20.5 is available, click Update to install the latest stable release
  6. 6. After updating, test critical site functionality to ensure the update did not break existing features
  7. 7. Verify that the vulnerability is resolved by confirming contributor-level users cannot perform admin-level actions
Caveat Always backup your site before updating; custom child theme modifications may need review after major theme updates

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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