CVE-2026-105993

validatingZero is analyzing and reversing it now.

GHSA-mgcf-822r-c8hf ↗EUVD-2026-115679 ↗

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.
DT Directory Lite Addon <= 1.1
ETK-2026-3343Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

DT Directory Lite Addon for WordPress is affected through version 1.1. An unauthenticated remote attacker may alter the plugin's configuration and skin options because settings requests are not adequately validated. Exploitation requires the plugin's vulnerable settings handlers to be reachable.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Deactivate and remove DT Directory Lite Addon version 1.1 or earlier until a vendor-fixed release is available and verified. Restrict public access to the WordPress site and administrative endpoints where feasible to reduce exposure.

check
building now
exploit
not yet
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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 06:00Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-11-03 06:00Z
    ghsa: trigger signal, started the run
  2. 2026-11-03 06:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3343",
  "cve_id": "CVE-2026-105993",
  "display_id": "CVE-2026-105993",
  "ghsa_id": "GHSA-mgcf-822r-c8hf",
  "euvd_id": "EUVD-2026-115679",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Unauthenticated settings modification in DT Directory Lite Addon",
  "summary": "DT Directory Lite Addon for WordPress is affected through version 1.1. An unauthenticated remote attacker may alter the plugin's configuration and skin options because settings requests are not adequately validated. Exploitation requires the plugin's vulnerable settings handlers to be reachable.",
  "mitigation": "Deactivate and remove DT Directory Lite Addon version 1.1 or earlier until a vendor-fixed release is available and verified. Restrict public access to the WordPress site and administrative endpoints where feasible to reduce exposure.",
  "vendor": null,
  "product": "DT Directory Lite Addon",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DT Directory Lite Addon",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-11-03T06:00:23.072000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T06:00:23.072000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T06:00:23.072000+00:00",
      "url": "https://github.com/advisories/GHSA-mgcf-822r-c8hf"
    }
  }
}

published 2026-11-03 06:46Z
last change 2026-11-03 07: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.