Skip to content
Fencer Vulns
medium 5.3

CVE-2023-45292 json

Captcha verification bypass in github.com/mojocn/base64Captcha

published 2023-12-08 2 y ago modified 2026-06-17 4 mo ago also GHSA-5mmw-p5qv-w3x5 , GO-2023-2386 , EUVD-2023-3117

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/mojocn/base64Captcha 1.3.6
  • github.com/mojocn/base64Captcha github.com/mojocn/base64Captcha 1.3.6

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/mojocn/base64Captcha/issues/120 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/mojocn/base64Captcha
<1.3.6
1.3.6

Affected products

  • github.com/mojocn/base64Captcha github.com/mojocn/base64Captcha

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-670 Always-Incorrect Control Flow Implementation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.