Improper Input Validation in sopel-plugins.channelmgnt

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.6 · CVSS:3.1/AV:A/AC:L/PR:H/UI:R/S:C/C:N/I:H/A:H

EPSS

• CVE-2021-21431: 1.08% estimated exploitation activity in the next 30 days; percentile 65.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact On some IRC servers, restrictions around the removal of the bot using the kick/kickban command could be bypassed when kicking multiple users at once. We also believe it may have been possible to remove users from other channels but due to the wonder that is IRC and following RfCs, We have no POC for that. Freenode is not affected. Patches Upgrade to 2.0.1 or higher Workarounds Do not use this plugin on networks where TARGMAX 1. For more information If you have any questions or comments about this advisory: Open an issue on phab. Email us at staff(at)mirahezebots(dot)org

Published by the source

9 Apr 2021, 15:42 UTC

Last modified by the source

13 Jul 2026, 12:14 UTC

Source last checked

26 Oct 2026, 13:23 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-23c7-6444-399m

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-23c7-6444-399m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-21431

Advisory: Improper Input Validation in sopel-plugins.channelmgnt
IDs: CVE-2021-21431, GHSA-23c7-6444-399m
Record: https://patchnext.com/advisories/cve-2021-21431 (revision 2, source checked 26 Oct 2026, 13:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sopel-plugins-channelmgnt 2.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI sopel-plugins-channelmgnt: affected < 2.0.1; fixed in 2.0.1

## Suggested inspection (read-only)
- `python -m pip show sopel-plugins-channelmgnt`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sopel-plugins-channelmgnt.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-23c7-6444-399m (OSV record GHSA-23c7-6444-399m lists affected ranges: PyPI sopel-plugins-channelmgnt >=0 <2.0.1 (fixed))
- Verified: https://github.com/advisories/GHSA-23c7-6444-399m (GitHub-reviewed advisory GHSA-23c7-6444-399m lists affected ranges: PyPI sopel-plugins-channelmgnt >=0 <2.0.1)

Commands are suggestions: review each one before running it.