CVE-2026-42713

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

EUVD-2026-94287 ↗

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.
Gopiplus Post title marquee scroll <= 9.9
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-870, permanent identifier
9d 21h 58msince last run
39mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+92h49m
0
+2h
+4h
+6h
+8h
+10h

description

Post title marquee scroll versions through 9.9 are affected by a blind SQL injection flaw. An attacker may be able to influence database queries; the required access level and attack path are not established by the available evidence.

mitigation

Disable and remove post-title-marquee-scroll from affected sites until an updated release is available. No fixed version is recorded; monitor the supplier's release information before re-enabling it.

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.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%12th percentile
agent run time
39m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 10:57Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-07 10:57Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-870",
  "cve_id": "CVE-2026-42713",
  "display_id": "CVE-2026-42713",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-94287",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Blind SQL injection in post-title-marquee-scroll",
  "summary": "Post title marquee scroll versions through 9.9 are affected by a blind SQL injection flaw. An attacker may be able to influence database queries; the required access level and attack path are not established by the available evidence.",
  "mitigation": "Disable and remove post-title-marquee-scroll from affected sites until an updated release is available. No fixed version is recorded; monitor the supplier's release information before re-enabling it.",
  "vendor": "Gopiplus",
  "product": "Post title marquee scroll",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 9.9"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "post-title-marquee-scroll",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 7.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L",
  "epss_score": 0.0023,
  "epss_percentile": 0.1253,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 38.66668105,
  "t0_at": "2026-10-07T10:57:33.366000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T10:57:33.366000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T10:57:33.366000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-42713"
    }
  }
}

published 2026-10-07 13:08Z
last change 2026-10-21 04:45Z

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.