CVE-2026-62031

validatedZero produced an exploit or a check.

GHSA-gf95-r66j-9vp4 ↗EUVD-2026-96466 ↗

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.+35d
Stylemix uListing <= 2.2.0
ETK-2026-4476Zero's internal tracking ID, independent of the CVE number., permanent identifier
+35dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
cve.org publicationtrigger signal +34dcheck available+35dkevagent stopped
0
+10d
+20d
+30d

description

Stylemix uListing versions through 2.2.0 are affected by an SQL injection flaw. An unauthenticated remote attacker may be able to influence database queries and infer protected data where the vulnerable functionality is reachable.

mitigation

Restrict public access to uListing functionality and deploy SQL-injection request filtering at a reverse proxy or WAF. Monitor for and apply a vendor-provided update when one is released; no fixed version is recorded in the advisory.

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.28%21st percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-10 19:35Z
Δ 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.
+35d

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-10 19:35Z
  2. 2026-11-14
    vulncheck_kev: trigger signal, started the run
  3. 2026-11-14 00:00Z
  4. 2026-11-14 16:47Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4476",
  "cve_id": "CVE-2026-62031",
  "display_id": "CVE-2026-62031",
  "ghsa_id": "GHSA-gf95-r66j-9vp4",
  "euvd_id": "EUVD-2026-96466",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated SQL injection in Stylemix uListing",
  "summary": "Stylemix uListing versions through 2.2.0 are affected by an SQL injection flaw. An unauthenticated remote attacker may be able to influence database queries and infer protected data where the vulnerable functionality is reachable.",
  "mitigation": "Restrict public access to uListing functionality and deploy SQL-injection request filtering at a reverse proxy or WAF. Monitor for and apply a vendor-provided update when one is released; no fixed version is recorded in the advisory.",
  "vendor": "Stylemix",
  "product": "uListing",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.2.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ulisting",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.3,
  "cvss_src": "other",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L",
  "epss_score": 0.0028,
  "epss_percentile": 0.2108,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.009159133333333333,
  "t0_at": "2026-10-10T19:35:31.204000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-14T16:47:43.914700+00:00",
      "days": 34.88348044791667,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:35:31.204000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-11-14T00:00:00+00:00",
      "days": 35,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:35:31.204000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-62031"
    },
    "trigger_signal": {
      "at": "2026-11-14T00:00:00+00:00",
      "days": 34.18366662037037,
      "is_lower_bound": false,
      "measured_at": "2026-10-10T19:35:31.204000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-62031"
    }
  }
}

published 2026-11-14 16:47Z
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.