LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31915: WordPress Flatsome theme <= 3.19.6 - Broken Access Control vulnerability

Missing 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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Some WordPress sites using the Flatsome theme through version 3.19.6 may not properly enforce authorization checks. The public record indicates possible unauthorized access to limited information, not site takeover or service disruption. It is rated medium severity, but any public site using this theme should be checked.

Executive priority

Treat this as a medium-priority exposure management item. Prioritize public ecommerce or brand-critical WordPress sites because exploitation requires no login. There is no provided evidence of active exploitation, so focus on inventory, version validation, and vendor-guided remediation.

Technical view

CVE-2026-31915 is a CWE-862 missing authorization issue in UX-themes Flatsome, affecting versions through 3.19.6. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, low confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is most likely on Internet-facing WordPress sites running the Flatsome theme at version 3.19.6 or earlier. The CVSS vector indicates unauthenticated remote reachability. The sources do not identify the vulnerable endpoint, feature, or specific data exposed.

Exploitation context

The CVE is not listed as KEV, and the provided sources do not report active exploitation or a public exploit. The risk comes from unauthenticated network access and missing authorization, but operational exploit details are not public in the provided bundle.

Researcher notes

Public details are limited. The sources identify missing authorization and affected versions through 3.19.6, but not the vulnerable component, endpoint, fixed version, proof of concept, or observed exploitation. Avoid assuming broader impact beyond low confidentiality exposure stated by CVSS.

Mitigation direction

  • Inventory WordPress sites using the UX-themes Flatsome theme.
  • Check each Flatsome version and flag 3.19.6 or earlier.
  • Review UX-themes and Patchstack guidance for a fixed release or mitigation.
  • Apply the vendor-supported update when available and tested.
  • Increase monitoring for unusual unauthenticated requests to affected WordPress sites.

Validation and detection

  • Confirm whether Flatsome is installed and active on each WordPress site.
  • Record the installed Flatsome version from administrative or asset inventory data.
  • Compare installed versions against the affected range: through 3.19.6.
  • Verify remediation against vendor or Patchstack advisory information.
  • Review web logs for suspicious unauthenticated access patterns, without attempting exploitation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-31915 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-31915Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
UX-themesFlatsomeflatsome, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.