Flatsome - Security Vulnerability (CVE-2026-117490)
CVE-2026-117490
The Flatsome WordPress theme before 3.20.13 does not enforce the acting user's publish and post-type restrictions on an AJAX save action, allowing users with a role as low as Contributor to publish their own content and change its post type (for example to a product) without holding the required capabilities.
CVE-2026-117490
LOW
CVSS 2.7
Published 2026-11-14
Updated 2026-11-17
AI Risk Low (32/100)
Active Exploit: No strong signal
Published Exploit: No public exploit references
Priority: P5 Monitor
Severity Band
LOW
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Affected Components
1
Reference Links
1
AI Risk Engine
Low (32/100)
Exploitability
High
Active Exploitation
No strong signal
Published Exploit Status
No public exploit references
AI Context
Machine-generated threat intelligence
AI
Updated just now
AI enriched just now (2026-11-17 17:49 UTC)
Technical Summary
The Flatsome WordPress theme before 3.20.13 does not enforce the acting user's publish and post-type restrictions on an AJAX save action, allowing users with a role as low as Contributor to publish their own content and change its post type (for example to a product) without holding the required capabilities.
Potential Impact
Severity is LOW (CVSS 2.7). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.
Exploitability Assessment
Exploitability is assessed as High based on remote code execution potential.
Primary risk drivers: remote code execution potential
Mitigation Recommendations
Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.
Detection & Monitoring
Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.
Business Impact Lens
AI risk score 32/100 (Low, High) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.