# CVE-2026-117487: Flatsome < 3.20.13 - Unauthenticated Unpublished Post Disclosure via flatsome_ajax_apply_shortcode

Status: published. Published: 2026-11-14. Updated: 2026-11-14.

The Flatsome WordPress theme before 3.20.13 does not perform a capability or nonce check on an AJAX action available to unauthenticated users, and does not restrict the status of the posts it returns by ID, allowing unauthenticated users to disclose the content of unpublished (draft and pending) posts.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / Flatsome: ≥ 0; < 3.20.13 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-200

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/0a75e026-f7dd-4436-8fc1-0614d320a8b8/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/0a75e026-f7dd-4436-8fc1-0614d320a8b8/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-117487; retrieved 2026-11-14; source updated 2026-11-14

Revision: 0948d7740298560a2da8c65d9660bfb1b7a3bde067991ac36ef54270a7f4d73e

Canonical: https://y2.dev/cve/CVE-2026-117487

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.