MyBB up to 1.8.39 Captcha contact.php invalidate_captcha captchaimage authentication replay
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in MyBB up to 1.8.39. It has been rated as critical. This affects the function captcha::invalidate_captcha of the file contact.php of the component Captcha. The manipulation of the argument captchaimage leads to authentication replay.
This vulnerability is documented as CVE-2026-45734. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in MyBB up to 1.8.39 and classified as critical. This issue affects the function captcha::invalidate_captcha of the file contact.php of the component Captcha. The manipulation of the argument captchaimage with an unknown input leads to a authentication replay vulnerability. Using CWE to declare the problem leads to CWE-294. A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
MyBB is free and open source forum software. Prior to 1.8.40, the built-in CAPTCHA does not consistently enforce single-use semantics, allowing remote attackers to bypass CAPTCHA controls through challenge replay. The successful validation paths in contact.php, member.php?action=do_resendactivation, member.php?action=do_lostpw, member.php?action=do_emailuser, and sendthread.php?action=do_sendtofriend do not call captcha::invalidate_captcha() for the MyBB Default CAPTCHA selected by the captchaimage setting. A valid response can therefore be reused until a non-vulnerable endpoint invalidates it, an incorrect response is submitted, or the challenge expires. This issue is fixed in version 1.8.40.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-45734 since 05/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/18/2026). The attack technique deployed by this issue is T1040 according to MITRE ATT&CK.
By approaching the search of inurl:contact.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.8.40 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 1.8.0
- 1.8.1
- 1.8.2
- 1.8.3
- 1.8.4
- 1.8.5
- 1.8.6
- 1.8.7
- 1.8.8
- 1.8.9
- 1.8.10
- 1.8.11
- 1.8.12
- 1.8.13
- 1.8.14
- 1.8.15
- 1.8.16
- 1.8.17
- 1.8.18
- 1.8.19
- 1.8.20
- 1.8.21
- 1.8.22
- 1.8.23
- 1.8.24
- 1.8.25
- 1.8.26
- 1.8.27
- 1.8.28
- 1.8.29
- 1.8.30
- 1.8.31
- 1.8.32
- 1.8.33
- 1.8.34
- 1.8.35
- 1.8.36
- 1.8.37
- 1.8.38
- 1.8.39
License
Website
- Product: https://mybb.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Authentication replayCWE: CWE-294 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: MyBB 1.8.40
Timeline
05/13/2026 CVE reserved08/18/2026 Advisory disclosed
08/18/2026 VulDB entry created
08/18/2026 VulDB entry last update
Sources
Product: mybb.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-45734 (🔒)
GCVE (CVE): GCVE-0-2026-45734
GCVE (VulDB): GCVE-100-391811
Entry
Created: 08/18/2026 18:27Changes: 08/18/2026 18:27 (67)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.