CVE-2026-22390
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Builderall Builderall Builder for WordPress builderall-cheetah-for-wp allows Code Injection.This issue affects Builderall Builder for WordPress: from n/a through <= 3.0.1.
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 in the Builderall Builder for WordPress plugin (builderall-cheetah-for-wp) versions up to 3.0.1 allows attackers to inject malicious code due to improper control of code generation. This critical flaw likely stems from unsanitized user input being dynamically evaluated or used in code construction, potentially enabling full site compromise including arbitrary code execution.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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.
-
Verify Builderall Builder plugin installation and versionCheck the plugin file header in wp-content/plugins/builderall-cheetah-for-wp/builderall-cheetah-for-wp.php for the 'Version' comment, or query the WordPress database wp_options table for the active_plugins option to list installed plugins and their versionsAffected if The plugin is installed and its version is 3.0.1 or lower (or if no version is returned, assume affected)
-
Confirm plugin is active on the WordPress siteQuery the wp_options table for the option_name 'active_plugins' and check if builderall-cheetah-for-wp/builderall-cheetah-for-wp.php appears in the serialized arrayAffected if The plugin is active and meets the version condition in step 1, indicating the vulnerable code can be reached
-
Identify dynamic code generation or evaluation functionsSearch the plugin directory for PHP functions that execute code dynamically, such as eval(), preg_replace() with /e modifier, extract(), create_function(), call_user_func(), or variable functions (e.g., $func()), using grep or a code analysis tool on the plugin source filesAffected if Any of these potentially dangerous functions are present and process user-supplied input without sanitization, indicating the vulnerability path exists
-
Check for signs of exploitation or malicious code injectionReview recent modifications to plugin files (check file timestamps), search for base64_decode(), shell_exec(), system(), exec(), or other suspicious patterns in plugin PHP files, and inspect the database for injected shortcodes or post content that may contain malicious payloadsAffected if Unexpected or recent file changes are found, or suspicious encoded code or command execution patterns are detected in plugin files or database entries
A user is affected if the Builderall Builder plugin (builderall-cheetah-for-wp) is installed, active, and running version 3.0.1 or lower that contains the vulnerable dynamic code generation routine.
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 dataUpdate Builderall Builder for WordPress to the latest version immediately. If no patched version exists, disable the plugin until a fix is available and review the code for input validation issues in dynamic code generation routines.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22390 — 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-22390 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