CVE-2025-67944
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 Nelio Software Nelio AB Testing nelio-ab-testing allows Code Injection.This issue affects Nelio AB Testing: from n/a through <= 8.1.8.
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 Nelio AB Testing WordPress plugin (versions up to 8.1.8) that allows an attacker to inject and execute arbitrary code. This improper control of code generation likely stems from insufficient input validation or unsafe eval/preg_replace usage within the plugin's A/B testing functionality.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Identify if Nelio AB Testing plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for a folder named 'nelio-ab-testing' or 'nelio-ab-testing-free' depending on the edition usedAffected if The plugin folder exists in the WordPress plugins directory
-
Determine the installed plugin versionOpen the main plugin PHP file (typically nelio-ab-testing.php or index.php in the plugin folder) and locate the version string in the plugin header comment, or check the readme.txt fileAffected if The version number is 8.1.8 or lower (any version up to and including 8.1.8)
-
Verify if the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and check if Nelio AB Testing is activated, or query the wp_options table for the active_plugins optionAffected if The plugin is activated and running on the WordPress site
-
Confirm A/B testing functionality is enabledCheck if there are any active A/B tests configured in the plugin settings (via WordPress admin dashboard under Nelio AB Testing menu) or inspect the wp_options table for nelioabtesting related options with active test configurationsAffected if A/B test functionality is actively configured or running on the site
-
Inspect plugin files for unsafe code patternsSearch within the plugin directory for use of eval(), preg_replace() with /e modifier, or similar code execution functions that may handle user input unsafely. Use grep or a code analysis tool to scan PHP files in the plugin folderAffected if Unsafe eval or preg_replace usage is found in the plugin code handling A/B test parameters
The environment is affected if Nelio AB Testing plugin version 8.1.8 or lower is installed and active with its A/B testing functionality enabled.
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 Nelio AB Testing to the latest patched version immediately. If no patch is available, disable the plugin or implement WAF rules to block malicious input patterns targeting the plugin's endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67944 — 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-2025-67944 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