CVE-2026-124833

waiting for further signalsZero needs more public information before it can validate it.

GHSA-cphg-5225-v7hq ↗EUVD-2026-124851 ↗

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.
Ahime Image Printer <= 1.0.0
ETK-2026-4354Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 00msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h59m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Ahime Image Printer for WordPress through version 1.0.0 does not adequately validate uploaded files. An unauthenticated attacker may upload arbitrary files and achieve code execution on the server where uploaded content can be executed. Exploitation requires the plugin's upload functionality to be reachable by the attacker.

mitigation

Disable and remove Ahime Image Printer from affected WordPress sites until a vendor-fixed release is available. Restrict public access to its upload functionality and ensure uploaded files cannot be executed by the web server.

check
no
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.
contextual
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
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-13 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-13 06:00Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4354",
  "cve_id": "CVE-2026-124833",
  "display_id": "CVE-2026-124833",
  "ghsa_id": "GHSA-cphg-5225-v7hq",
  "euvd_id": "EUVD-2026-124851",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated arbitrary file upload in Ahime Image Printer",
  "summary": "Ahime Image Printer for WordPress through version 1.0.0 does not adequately validate uploaded files. An unauthenticated attacker may upload arbitrary files and achieve code execution on the server where uploaded content can be executed. Exploitation requires the plugin's upload functionality to be reachable by the attacker.",
  "mitigation": "Disable and remove Ahime Image Printer from affected WordPress sites until a vendor-fixed release is available. Restrict public access to its upload functionality and ensure uploaded files cannot be executed by the web server.",
  "vendor": null,
  "product": "Ahime Image Printer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Ahime Image Printer",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.241075666666667,
  "t0_at": "2026-11-13T06:00:09.349000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-13T06:00:09.349000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-13T06:00:09.349000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-124833"
    }
  }
}

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