LiveActive security incident?Get immediate response
CVE Record

CVE-2010-4626: The my_rand function in functions.php in MyBB (aka MyBulletinBoard) before 1.4.12 does not properly use the...

The my_rand function in functions.php in MyBB (aka MyBulletinBoard) before 1.4.12 does not properly use the PHP mt_rand function, which makes it easier for remote attackers to obtain access to an arbitrary account by requesting a reset of the account's password, and then conducting a brute-force attack.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Older MyBB forum installations before 1.4.12 used weak randomness in the password reset flow. An attacker could request a password reset and more feasibly guess the reset value, potentially taking over any account. The sources do not show active exploitation or CVSS, but the impact is account compromise on exposed forums. Exposure is limited to MyBB, also known as MyBulletinBoard, versions before 1.4.12. Risk is most relevant for internet-facing forums with password reset enabled and valuable administrator or moderator accounts. The provided affected-product metadata is sparse, so confirm product and version directly. Prioritize remediation for any externally reachable MyBB forum still running before 1.4.12, especially where privileged accounts manage customer-facing content or user data. The business risk is account takeover, not service disruption. Lack of active exploitation evidence lowers urgency compared with KEV items, but obsolete internet-facing forum software should be closed quickly. Mitigation focus: Upgrade MyBB installations before 1.4.12 to 1.4.12 or later vendor-supported releases.; Review MyBB 1.4.12 security release guidance for any additional required maintenance steps.; Identify and retire legacy MyBB 1.4.x instances that are no longer maintained..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2010-4626 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.