From CVE Record to External Exposure
MyBB is a free and open source forum software. In affected versions the Admin CP's Settings management module does not validate setting types correctly on insertion and update, making it possible to add settings of supported type `php` with PHP code, executed on on _Change Settings_ pages. This results in a Remote Code Execution (RCE) vulnerability. The vulnerable module requires Admin CP access with the `Can manage settings?` permission. MyBB's Settings module, which allows administrators to add, edit, and delete non-default settings, stores setting data in an options code string ($options_code; mybb_settings.optionscode database column) that identifies the setting type and its options, separated by a new line character (\n). In MyBB 1.2.0, support for setting type php was added, for which the remaining part of the options code is PHP code executed on Change Settings pages (reserved ...
Mybb vulnerability should be triaged by matching the affected vendor and product to live, internet-facing assets rather than treating the CVE as an abstract feed item. ThreatPort focuses on the first question that budget-constrained IT leaders and CISOs ask: what can an outside observer find today, how severe is it, and what should be fixed first?
Known Exploitation Record
- Known ransomware campaign use
- Not recorded
- EPSS exploitation probability
- 77.68% (100p)
- CVSS base score
- 7.2 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H)
- Disclosed
- 2022-03-09
- Weakness type
- CWE-94
Source: CISA Known Exploited Vulnerabilities catalog and FIRST.org EPSS.
What ThreatPort Checks
The output is intentionally practical: ownership clues, risk context, remediation hints, and repeatable evidence that can be shared with technical teams or leadership. It is not positioned as magic compliance automation or a replacement for human security judgment.
Lean security teams rarely need another broad vulnerability list. They need to know whether an exposed endpoint, an expired certificate, a weak DNS setting, or a CVE-linked service is likely to affect the systems they actually run. ThreatPort scans from the outside in, ranks what it finds by real reachability rather than raw CVSS, and hands back evidence a team can act on the same day.
Route-Specific Evidence Profile
CVE-2022-24734 affects Mybb, a CWE-94 weakness. Disclosed 2022-03-09. This page exists to answer one question: is anything you own externally reachable and running it.
Assets This Page Should Care About
Signals Worth Prioritizing
What Should Be Reviewed First in This Context?
For teams running Mybb, the first step is to validate internet-facing assets with business relevance instead of producing a generic vulnerability list.
Action Checklist
- Confirm whether Mybb is present on any public domain, subdomain, API, or admin surface.
- Prioritize HIGH exposure only when the affected service is reachable or business-critical.
- Patch, disable, isolate, or put compensating controls in front of the affected service.
- Re-scan after remediation to capture before-and-after evidence for technical teams or leadership.
Context-Aware Next Fixes
- Verify ownership of exposed assets
- Close unnecessary public services
- Remediate the highest-confidence exposed findings first, then re-scan to prove closure.
Useful evidence for this context usually maps to ISO 27001, SOC 2, vendor security reviews. ThreatPort keeps the language cautious: this is operational security evidence, not a legal certification or a guarantee that every auditor will accept a generated report without review.