Description
### Impact
The registration component does not validate the text-based _Security Question_ CAPTCHA correctly, allowing attackers to bypass the challenge via a specially crafted value.


[CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)

### Details
The public _Registration_ workflow ([`member.php?action=do_register`](https://github.com/mybb/mybb/blob/mybb_1839/member.php#L262-L307)) accepts a hidden field `question_id` — expected to match the question session identifier (`mybb_questionsessions.sid`) — and validates the challenge answer without a fail-closed fallback for invalid identifiers. If the value is blank, forged, or expired, the request continues without a question-related error.

### Patches
MyBB 1.8.(...) resolves this issue with the following changes:

- Commit: https://github.com/mybb/mybb/commit/
- `.patch`: https://github.com/mybb/mybb/commit/.patch

### References
- Release Notes: https://mybb.com/versions/1.8.(...)/

### For more information
Go to [mybb.com/security](https://mybb.com/security/) to report possible security concerns or to learn more about security research at MyBB.

### Contact
The security team can be reached at [security@mybb.com](mailto:security@mybb.com).
Published: 2026-08-18
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

This vulnerability in MyBB’s registration workflow allows an attacker to bypass the security question CAPTCHA because the system does not enforce a strict check on the hidden field that stores the question session identifier. As a result, an attacker can submit forged or empty values for the security question, causing the registration process to proceed without verifying the answer. The weakness is categorized as CWE‑636 (Improper Validation of Directives). While the impact on confidentiality is none, the flaw can lead to unauthorized account creation and potential subsequent abuse of those accounts, representing a low integrity compromise in the CVSS 3.1 rating.

Affected Systems

The flaw affects MyBB production releases prior to version 1.8.40, including all 1.8.x builds that have not applied the 1.8.40 release or the associated patch commit. Vendors identified include the MyBB community repository. Users of earlier 1.8.x versions who have not yet migrated to 1.8.40 or later are in scope.

Risk and Exploitability

The CVSS score of 5.3 indicates a medium severity flaw. The likely attack vector is directly posting to the registration endpoint, and based on the description, it is inferred that no special privileges or UI interaction are required. Because the EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, the immediate threat level is moderate. The flaw can be leveraged to build a wholesale base of unauthenticated accounts, which can then be used for spam, phishing, or other downstream attacks. Admins should treat this as a reversible risk that can be mitigated by applying the vendor patch.

Generated by OpenCVE AI on August 18, 2026 at 18:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update MyBB to version 1.8.40 or later, which contains the regression fix for the security question validation.
  • Disable or throttle new user registrations temporarily while the update is applied, or install a plug‑in that adds a fail‑closed validation for the security question field.
  • After updating, audit newly created accounts for potential misuse and enforce a forced password reset or additional verification for all accounts created during the vulnerable period.

Generated by OpenCVE AI on August 18, 2026 at 18:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 20 Aug 2026 02:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 18 Aug 2026 18:15:00 +0000

Type Values Removed Values Added
First Time appeared Mybb
Mybb mybb
Vendors & Products Mybb
Mybb mybb

Tue, 18 Aug 2026 16:00:00 +0000

Type Values Removed Values Added
Description ### Impact The registration component does not validate the text-based _Security Question_ CAPTCHA correctly, allowing attackers to bypass the challenge via a specially crafted value. [CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) ### Details The public _Registration_ workflow ([`member.php?action=do_register`](https://github.com/mybb/mybb/blob/mybb_1839/member.php#L262-L307)) accepts a hidden field `question_id` — expected to match the question session identifier (`mybb_questionsessions.sid`) — and validates the challenge answer without a fail-closed fallback for invalid identifiers. If the value is blank, forged, or expired, the request continues without a question-related error. ### Patches MyBB 1.8.(...) resolves this issue with the following changes: - Commit: https://github.com/mybb/mybb/commit/ - `.patch`: https://github.com/mybb/mybb/commit/.patch ### References - Release Notes: https://mybb.com/versions/1.8.(...)/ ### For more information Go to [mybb.com/security](https://mybb.com/security/) to report possible security concerns or to learn more about security research at MyBB. ### Contact The security team can be reached at [security@mybb.com](mailto:security@mybb.com).
Title MyBB: Security Question insufficient validation
Weaknesses CWE-636
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-18T17:46:31.511Z

Reserved: 2026-05-14T18:06:06.810Z

Link: CVE-2026-46482

cve-icon Vulnrichment

Updated: 2026-08-18T17:44:41.496Z

cve-icon NVD

Status : Received

Published: 2026-08-18T16:17:09.350

Modified: 2026-08-18T18:17:38.290

Link: CVE-2026-46482

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T18:45:03Z

Weaknesses
  • CWE-636

    Not Failing Securely ('Failing Open')