CVE-2026-117492

waiting for further signalsZero needs more public information before it can validate it.

GHSA-p66x-489f-mxm6 ↗EUVD-2026-128442 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Flatsome < 3.20.13
fixed in 3.20.13
ETK-2026-4768Zero's internal tracking ID, independent of the CVE number., permanent identifier
14h 07msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h47m
0
+4h
+6h
+8h
+10h
+12h

description

Flatsome versions before 3.20.13 can store unsafe post metadata submitted through an AJAX action and later render it on product pages. An authenticated user with Contributor-level access can cause browser-side code to run for users who view an affected product page, including administrators.

mitigation

Update Flatsome to version 3.20.13 or later. Until updating, restrict Contributor and other untrusted accounts from editing content or product metadata.

fixed in 3.20.13

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-18 06:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-18 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-18 06:00Z

this entry in the feed

GET /api/v1/feed/CVE-2026-117492

{
  "etk_id": "ETK-2026-4768",
  "cve_id": "CVE-2026-117492",
  "display_id": "CVE-2026-117492",
  "ghsa_id": "GHSA-p66x-489f-mxm6",
  "euvd_id": "EUVD-2026-128442",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in Flatsome WordPress theme",
  "summary": "Flatsome versions before 3.20.13 can store unsafe post metadata submitted through an AJAX action and later render it on product pages. An authenticated user with Contributor-level access can cause browser-side code to run for users who view an affected product page, including administrators.",
  "mitigation": "Update Flatsome to version 3.20.13 or later. Until updating, restrict Contributor and other untrusted accounts from editing content or product metadata.",
  "vendor": null,
  "product": "Flatsome",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.20.13"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.20.13"
      ],
      "package_name": "Flatsome",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.1618133,
  "t0_at": "2026-11-18T06:00:07.243000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-18T06:00:07.243000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-18T06:00:07.243000+00:00",
      "url": "https://github.com/advisories/GHSA-p66x-489f-mxm6"
    }
  }
}

published 2026-11-18 07:25Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.