← back to feed
CVE-2026-96768

CVE-2026-96768

validatedZero produced an exploit or a check.

GHSA-fgfc-hpw9-v2pq ↗EUVD-2026-102830 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
softaculous GoSMTP Pro <= 1.2.3
ETK-2026-2147Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss7.2cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
+4.0dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+4.0dagent stopped
0
+1d
+2d
+3d

description

GoSMTP Pro for WordPress through version 1.2.3 can store unsafe comment-derived content in its email logs. An unauthenticated attacker may cause browser script execution when a user views an affected logged page, provided the attacker can submit comment content that is processed into the log.

mitigation

Disable GoSMTP Pro until the vendor publishes an update; no fixed version is recorded. If it must remain enabled, limit untrusted comment submission and restrict access to email-log pages.

check
available
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.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.19%8th percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 09:26Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-10-16 09:26Z
    ghsa: trigger signal, started the run
    https://github.com/advisories/GHSA-fgfc-hpw9-v2pq
  2. 2026-10-16 09:26Z
  3. 2026-10-20 09:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2147",
  "cve_id": "CVE-2026-96768",
  "display_id": "CVE-2026-96768",
  "ghsa_id": "GHSA-fgfc-hpw9-v2pq",
  "euvd_id": "EUVD-2026-102830",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Stored cross-site scripting in GoSMTP Pro email logs",
  "summary": "GoSMTP Pro for WordPress through version 1.2.3 can store unsafe comment-derived content in its email logs. An unauthenticated attacker may cause browser script execution when a user views an affected logged page, provided the attacker can submit comment content that is processed into the log.",
  "mitigation": "Disable GoSMTP Pro until the vendor publishes an update; no fixed version is recorded. If it must remain enabled, limit untrusted comment submission and restrict access to email-log pages.",
  "vendor": "softaculous",
  "product": "GoSMTP Pro",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.2.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "GoSMTP Pro",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
  "epss_score": 0.0019,
  "epss_percentile": 0.0818,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.009951283333333333,
  "t0_at": "2026-10-16T09:26:36.859000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-20T09:17:28.212655+00:00",
      "days": 3.9936499265625,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T09:26:36.859000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-16T09:26:36.859000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T09:26:36.859000+00:00",
      "url": "https://github.com/advisories/GHSA-fgfc-hpw9-v2pq"
    }
  }
}

published 2026-10-20 09:17Z
last change 2026-10-21 11:52Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.