← back to feed
CVE-2026-103367

CVE-2026-103367

validatedZero produced an exploit or a check.

GHSA-fqgv-5m94-gg38 ↗EUVD-2026-100903 ↗

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.
wpdesk ShopMagic – email automation for WordPress <= 4.9.0
CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
ETK-2026-1752Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.1cna vendorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
+2.0dTTV
50mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0dcheck available+2.0dagent stopped
0
+1d

description

ShopMagic for WordPress through version 4.9.0 can allow an unauthenticated party to cause server-side PHP files to be included, potentially exposing data, bypassing controls, or executing code already present on the server. Exposure requires a published ShopMagic recipe that evaluates the customer's first-name field, and the bundled new-order social-profile email recipe is reported to satisfy that requirement.

mitigation

Disable or unpublish ShopMagic recipes that evaluate the customer first-name field, including the affected bundled email recipe. Until a vendor-fixed release is available, restrict guest checkout or disable the plugin to reduce unauthenticated exposure.

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.
1.0%62nd percentile
agent run time
50m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 07:43Z
Δ 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-14 07:43Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-103367

this entry in the feed

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

{
  "etk_id": "ETK-2026-1752",
  "cve_id": "CVE-2026-103367",
  "display_id": "CVE-2026-103367",
  "ghsa_id": "GHSA-fqgv-5m94-gg38",
  "euvd_id": "EUVD-2026-100903",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated local file inclusion in ShopMagic",
  "summary": "ShopMagic for WordPress through version 4.9.0 can allow an unauthenticated party to cause server-side PHP files to be included, potentially exposing data, bypassing controls, or executing code already present on the server. Exposure requires a published ShopMagic recipe that evaluates the customer's first-name field, and the bundled new-order social-profile email recipe is reported to satisfy that requirement.",
  "mitigation": "Disable or unpublish ShopMagic recipes that evaluate the customer first-name field, including the affected bundled email recipe. Until a vendor-fixed release is available, restrict guest checkout or disable the plugin to reduce unauthenticated exposure.",
  "vendor": "wpdesk",
  "product": "ShopMagic – email automation for WordPress",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 4.9.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "ShopMagic – email automation for WordPress",
      "purl": null
    }
  ],
  "cwes": [
    98
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0101,
  "epss_percentile": 0.6247,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 49.90055098333333,
  "t0_at": "2026-10-14T07:43:32.923000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-16T07:30:03.881073+00:00",
      "days": 1.9906360888078705,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T07:43:32.923000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-14T07:43:32.923000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T07:43:32.923000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-103367"
    }
  }
}

published 2026-10-16 06:40Z
last change 2026-10-21 14:33Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.