CVE-2026-29202
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 · uneditedInsufficient input validation of the `plugin` parameter of the `create_user` plugin allows arbitrary Perl code execution on behalf of the already authenticated account's system user.
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 confidenceThe create_user plugin lacks proper input validation on the plugin parameter, allowing an authenticated attacker to inject and execute arbitrary Perl code on the host system. This code executes with the privileges of the system user account associated with the authenticated session.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 create_user plugin presenceLocate and list all installed plugins or modules named 'create_user' in your system. Search plugin directories for files related to user creation functionality.Affected if The create_user plugin is installed and accessible to authenticated users.
-
Verify plugin parameter handlingExamine the code or configuration that processes the 'plugin' parameter in the create_user functionality. Look for input validation routines that handle this parameter.Affected if The plugin parameter accepts user-supplied input without strict allowlist validation.
-
Inspect plugin loading mechanismReview how plugins are loaded and executed. Check if dynamic plugin loading is enabled and whether user-controlled input can influence which plugin gets loaded.Affected if Dynamic plugin loading is enabled and the plugin parameter can be manipulated by authenticated users.
-
Check authentication and authorization controlsReview the authentication mechanism and session privileges associated with the create_user functionality. Determine which authenticated users can access this feature.Affected if Authenticated users with valid sessions can access the create_user plugin functionality.
-
Audit Perl interpreter interactionExamine how the plugin parameter is passed to the Perl interpreter. Look for code paths where the parameter might be evaluated or executed as Perl code.Affected if The plugin parameter value is passed directly to a Perl interpreter without sanitization.
Your environment is affected if the create_user plugin is present, accepts user-controlled input for the plugin parameter, and executes it through a Perl interpreter without strict allowlist validation.
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 dataImplement strict allowlist-based validation for the plugin parameter and sanitize all user-supplied input before passing it to any interpreter. Consider disabling dynamic plugin loading or isolating plugin execution in a sandboxed environment.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-29202 — 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-29202 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