CVE-2026-106013

validatedZero produced an exploit or a check.

EUVD-2026-111538 ↗

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.
artbees Jupiter X Core <= 4.61.0
CWE-287 Improper Authentication
ETK-2026-2821Zero's internal tracking ID, independent of the CVE number., permanent identifier
+33mTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+33magent stopped
0
+10min
+20min
+30min

description

Jupiter X Core through version 4.61.0 is affected by an authentication bypass in its Twitter/X social-login feature. An unauthenticated attacker may obtain a WordPress session for the account associated with the configured X application owner, typically an administrator, when that social-login integration is enabled and configured.

mitigation

Disable the Twitter/X social-login integration until a corrected Jupiter X Core release is available. Review active sessions and privileged accounts for unexpected access.

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.
–
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 01:30Z
Δ 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-28 01:30Z
    cve_org: trigger signal, started the run
  2. 2026-10-28 02:04Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2821",
  "cve_id": "CVE-2026-106013",
  "display_id": "CVE-2026-106013",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-111538",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Jupiter X Core social login",
  "summary": "Jupiter X Core through version 4.61.0 is affected by an authentication bypass in its Twitter/X social-login feature. An unauthenticated attacker may obtain a WordPress session for the account associated with the configured X application owner, typically an administrator, when that social-login integration is enabled and configured.",
  "mitigation": "Disable the Twitter/X social-login integration until a corrected Jupiter X Core release is available. Review active sessions and privileged accounts for unexpected access.",
  "vendor": "artbees",
  "product": "Jupiter X Core",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.61.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Jupiter X Core",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.2618816666666667,
  "t0_at": "2026-10-28T01:30:48.320000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-28T02:04:06.379895+00:00",
      "days": 0.023125693229166668,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T01:30:48.320000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-28T01:30:48.320000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T01:30:48.320000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106013"
    }
  }
}

published 2026-10-28 02:03Z
last change 2026-10-28 02:59Z

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.