Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

GHSA-23c7-6444-399m is a high-severity (CVSS 7.6) Improper Input Validation vulnerability in sopel-plugins-channelmgnt. O3 Security confirms whether GHSA-23c7-6444-399m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Input Validation in sopel-plugins.channelmgnt

Also known asCVE-2021-21431PYSEC-2021-58
Published
Apr 9, 2021
Updated
Jul 13, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 13, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍sopel-plugins-channelmgnt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIsopel-plugins-channelmgntall versions2.0.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sopel-plugins-channelmgnt. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update sopel-plugins-channelmgnt to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-23c7-6444-399m is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-23c7-6444-399m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-23c7-6444-399m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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](https://phab.mirahezebots.org/man
O3 Security · Impact-Aware SCA

Is GHSA-23c7-6444-399m in your dependencies?

O3 detects GHSA-23c7-6444-399m across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.