CVE
immonex Kickstart unauthenticated file inclusion via cidata parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The immonex Kickstart plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.19.0 via the 'inx-r-cidata (JSON blob containing 'template' and 'template_folders')' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The filename-level sanitization that strips dot-slash sequences applies only to the template filename component, not to the attacker-supplied template_folders directory paths, rendering it ineffective against directory traversal via that parameter.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123419 (immonex Kickstart <= 1.19.0 - Unauthenticated Local File Inclusion via 'inx-r-cidata' Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-123419 (entry last updated 2026-11-18):
Affected:
- immonex immonex Kickstart: through 1.19.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123419 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123419 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/cac5e7fe-3f23-4f3c-bd9b-bfc23a396186?source=cve
- https://plugins.trac.wordpress.org/browser/immonex-kickstart/tags/1.18.0/vendor/immonex/wp-free-plugin-core/src/V2_14_1/class-template-utils.php#L147
- https://plugins.trac.wordpress.org/browser/immonex-kickstart/tags/1.18.0/vendor/immonex/wp-free-plugin-core/src/V2_14_1/class-template-utils.php#L662
- https://plugins.trac.wordpress.org/browser/immonex-kickstart/tags/1.18.0/includes/class-rest-api.php#L193
- https://plugins.trac.wordpress.org/browser/immonex-kickstart/tags/1.18.0/includes/class-rest-api.php#L63
- https://plugins.trac.wordpress.org/browser/immonex-kickstart/tags/1.18.0/includes/class-property-list.php#L110
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3789524%40immonex-kickstart%2Ftags%2F1.19.0&old=3711261%40immonex-kickstart%2Ftags%2F1.18.0
- https://plugins.trac.wordpress.org/changeset?reponame=&new=3789592%40immonex-kickstart%2Ftags%2F1.19.1&old=3711261%40immonex-kickstart%2Ftags%2F1.18.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-123419
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123419"}.Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- First seen by cve.now
Affected versions
- immonex immonex Kickstart
through 1.19.0
Evidence 10
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123419
Is CVE-2026-123419 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123419?
immonex Kickstart: through 1.19.0.Source: cve.now feed data