CVE-2026-30309
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 · uneditedInfCode's terminal auto-execution module contains a critical command filtering vulnerability that renders its blacklist security mechanism completely ineffective. The predefined blocklist fails to cover native high-risk commands in Windows PowerShell (such as powershell), and the matching algorithm lacks dynamic semantic parsing unable to recognize string concatenation, variable assignment, or double-quote interpolation in Shell syntax. Malicious commands can bypass interception through simple syntax obfuscation. An attacker can construct a file containing malicious instructions for remote code injection. When a user imports and views such a file in the IDE, the Agent executes dangerous PowerShell commands outside the blacklist without user confirmation, resulting in arbitrary command execution or sensitive data leakage.
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 confidenceInfCode's terminal auto-execution module uses an ineffective blacklist-based command filter that fails to block PowerShell and cannot detect syntax obfuscation via string concatenation, variable assignment, or double-quote interpolation. When a user imports a malicious file containing obfuscated commands, the IDE's Agent executes them without confirmation, enabling arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.3.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify the installed InfCode IDE versionCheck the application version through its built-in About dialog, help menu, or the executable file properties (right-click the InfCode executable, select Properties, then view the Details tab for Version information)Affected if The version is 1.3.1 or lower (any version <= 1.3.1)
-
Locate the terminal auto-execution module configurationExamine the InfCode IDE settings or configuration files for any terminal-related settings, particularly those related to auto-execution, command execution, or agent functionalityAffected if The auto-execution feature is present and enabled in the configuration
-
Inspect the command blacklist configurationSearch through InfCode's configuration files, settings, or security preferences for any blacklist or whitelist of permitted terminal commandsAffected if No PowerShell commands are included in the blacklist, or the blacklist is empty/missing
-
Check for user confirmation settings before command executionReview the IDE security or terminal settings for any prompts or confirmation dialogs that should appear before executing terminal commandsAffected if User confirmation is disabled or not required before executing imported commands
-
Review recently imported files for obfuscated commandsExamine any recently imported project files, scripts, or configuration files that may have been loaded into InfCode for signs of PowerShell commands using obfuscation techniques such as string concatenation ($env:var + "cmd"), variable assignment, or double-quote interpolationAffected if Files contain PowerShell commands with obfuscation patterns and these commands have been executed automatically
A user is affected if they are running Tokfinity Infcode version 1.3.1 or lower with the terminal auto-execution module enabled and without PowerShell properly blacklisted or user confirmation required before command execution.
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 blacklist with an allowlist approach that includes semantic parsing to recognize obfuscation techniques, or implement mandatory user confirmation before executing any terminal commands, particularly PowerShell invocations.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30309 — 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-30309 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