CVE-2026-9302
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was determined in 546669204 vps-inventory-monitoring up to 98c00b370668c96ae75e91c15548d9ea113652d9. This issue affects the function eval of the file app/index/command/VpsTest.php of the component VpsTest Console. Executing a manipulation of the argument vf can lead to code injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA code injection vulnerability exists in the VpsTest Console component of vps-inventory-monitoring. The 'vf' argument passed to the eval() function in app/index/command/VpsTest.php is not properly sanitized, allowing remote attackers to inject and execute arbitrary PHP code. This is a critical security flaw as eval() directly executes strings as code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the vulnerable VpsTest component fileSearch for the file app/index/command/VpsTest.php in your application installation directory. This is the file containing the vulnerable eval() call.Affected if The file exists in your environment - the application uses this console component.
-
Identify if the eval() vulnerability is presentOpen app/index/command/VpsTest.php and search for eval() calls that process the 'vf' parameter without sanitization. Look for patterns like eval($vf) or eval($_GET['vf']).Affected if The code contains an eval() call directly using the 'vf' user input parameter without validation or sanitization functions.
-
Check if the VpsTest console is accessibleDetermine if the VpsTest console component is exposed via web access or CLI. Check routing/console configuration files for VpsTest command registration and access controls.Affected if The VpsTest console command is accessible without proper authentication or access restrictions.
-
Determine application versionCheck your installed version of vps-inventory-monitoring by reviewing version files, composer.json, or git tags in the application root directory.Affected if Your installed version matches or predates the version containing this vulnerability (compare against the version that includes the fix for CVE-2026-9302).
You are affected if the VpsTest.php file exists with an unsanitized eval() processing the 'vf' parameter, and this console component is accessible to unauthenticated or untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the eval() usage with safe alternatives such as a whitelist approach, parameterized processing, or refactored logic that does not require dynamic code execution. Implement strict input validation on the 'vf' argument before any processing occurs.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9302 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9302 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data