CVE-2026-93953

validatedZero produced an exploit or a check.

GHSA-p347-j652-996x ↗EUVD-2026-102613 ↗

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 Backuply – Backup, Restore, Migrate and Clone <= 1.5.8
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-1836Zero's internal tracking ID, independent of the CVE number., permanent identifier
+23h48mTTV
22mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+23h48magent stopped
0
+6h
+12h
+18h

description

Backuply for WordPress through version 1.5.8 can embed untrusted profile data into backup database dumps and execute it when an administrator restores the backup. An authenticated user with subscriber-level access or greater could modify site database data, potentially leading to administrator-level access, if a backup containing their data is restored.

mitigation

Update Backuply to version 1.5.9 or later. Until updates are complete, restrict low-privilege account creation and access, and do not restore backups that may contain untrusted user profile data.

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%25th percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 03:38Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-16 03:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1836",
  "cve_id": "CVE-2026-93953",
  "display_id": "CVE-2026-93953",
  "ghsa_id": "GHSA-p347-j652-996x",
  "euvd_id": "EUVD-2026-102613",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Second-order SQL injection in Backuply",
  "summary": "Backuply for WordPress through version 1.5.8 can embed untrusted profile data into backup database dumps and execute it when an administrator restores the backup. An authenticated user with subscriber-level access or greater could modify site database data, potentially leading to administrator-level access, if a backup containing their data is restored.",
  "mitigation": "Update Backuply to version 1.5.9 or later. Until updates are complete, restrict low-privilege account creation and access, and do not restore backups that may contain untrusted user profile data.",
  "vendor": "softaculous",
  "product": "Backuply – Backup, Restore, Migrate and Clone",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.5.8"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Backuply – Backup, Restore, Migrate and Clone",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": 0.0034,
  "epss_percentile": 0.2597,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 22.3557694,
  "t0_at": "2026-10-16T03:38:40.799000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-17T03:26:33.731313+00:00",
      "days": 0.9915848647337963,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T03:38:40.799000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-16T03:38:40.799000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T03:38:40.799000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-93953"
    }
  }
}

published 2026-10-17 03:04Z
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.