CVE-2026-31915
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 · uneditedMissing Authorization vulnerability in UX-themes Flatsome flatsome allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Flatsome: from n/a through <= 3.19.6.
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 confidenceMissing Authorization vulnerability in the Flatsome WordPress theme allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in versions up to 3.19.6 and enables unauthorized access to certain functionality or data due to improper or missing authorization checks.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Flatsome theme versionNavigate to WordPress admin > Appearance > Themes and locate the Flatsome theme to view its version. Alternatively, open wp-content/themes/flatsome/style.css and check the 'Version' header comment.Affected if The installed version is 3.19.6 or earlier.
-
Locate AJAX endpoints in the themeSearch the Flatsome theme directory (wp-content/themes/flatsome) for PHP files containing 'wp_ajax_' or 'wp_ajax_nopriv_' action hooks. These define endpoints that handle frontend requests.Affected if AJAX endpoints exist that lack capability checks or nonce verification.
-
Verify authorization on admin functionsExamine theme PHP files that handle admin-side functionality (typically in /inc/ or /classes/ directories). Look for functions that perform sensitive operations and check if they include current_user_can() capability checks before executing.Affected if Sensitive admin functions are accessible without proper capability verification.
-
Test for unauthenticated access to restricted featuresIf you have identified specific AJAX endpoints or admin actions from the theme, attempt to call them without authenticating or without proper user privileges to see if they execute.Affected if The endpoints execute actions without verifying user authorization.
A user is affected if the Flatsome theme version is 3.19.6 or earlier and sensitive AJAX endpoints or admin functions lack proper authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Flatsome theme to the latest version (3.19.7 or later) which contains the security fix. If immediate update is not possible, audit all admin-side functions and AJAX endpoints for proper capability checks and nonce verification.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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