NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Always incorrect control flow in github.com/mojocn/base64CaptchaGHSA-5mmw-p5qv-w3x5

MEDIUMFix: mojocn/base64Captcha@5ab86bd

GHSA-5mmw-p5qv-w3x5 is a medium-severity (CVSS 5.3) CWE-345 vulnerability in github.com/mojocn/base64Captcha. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/mojocn/base64Captcha — see the affected versions and patch details below.

Also known asCVE-2023-45292GO-2023-2386
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk
0.00%0.27%0.53%0.80%0.1%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/mojocn/base64Captcha

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

Description

When using the default implementation of Verify to check a Captcha, verification can be bypassed. For example, if the first parameter is a non-existent id, the second parameter is an empty string, and the third parameter is true, the function will always consider the Captcha to be correct.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/mojocn/base64Captchaall versions1.3.6go get github.com/mojocn/base64Captcha@v1.3.6

Affected Products

1 product · 1 configurations
Application
base64captchamojotv
< 1.3.6
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

When using the default implementation of Verify to check a Captcha, veri…

github.comNVDDec 2023

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mojocn/base64Captcha, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/mojocn/base64Captcha to 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5mmw-p5qv-w3x5 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.

Frequently Asked Questions

When using the default implementation of Verify to check a Captcha, verification can be bypassed. For example, if the first parameter is a non-existent id, the second parameter is an empty string, and the third parameter is true, the function will always consider the Captcha to be correct.
O3 Security · Impact-Aware SCA

Is GHSA-5mmw-p5qv-w3x5 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Always incorrect control flow in github.com/mojocn/base6…