dbcve.org
MybbApplication

CVE-2025-29460

HIGH · 7.6 CVSS v3.1 Published 2025-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in MyBB 1.8.38 allows a remote attacker to obtain sensitive information via the Add Mycode function. NOTE: the Supplier disputes this because of the allowed actions of Board administrators and because of SSRF mitigation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

MyBB 1.8.38 contains an information disclosure vulnerability in the Add Mycode admin function that allows remote attackers to obtain sensitive information. The vendor disputes this CVE, asserting the affected functionality is only accessible to Board administrators and that SSRF mitigations are in place. The high CVSS score suggests unauthenticated or low-privilege access may be achievable, or that internal network information can be leaked through the MyCode parsing mechanism.

MitigationIf the Add Mycode function should be restricted to authenticated administrators only, enforce proper authentication and authorization controls. If SSRF is involved, implement stricter URL validation and network segmentation to prevent internal resource disclosure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MybbApplication
Affected:= 1.8.38

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MyBB version
    Locate the version file in your MyBB installation - typically in /inc/class_core.php or check the admin dashboard under 'Home > Dashboard' which displays the installed version.
    Affected if The installed version is exactly 1.8.38
  2. Verify admin access controls
    Attempt to access the admin panel at /admin/index.php without authentication, or check the 'config' table in the MyBB database for 'allow_admin_login' or similar authorization settings.
    Affected if The admin panel or Add Mycode function is accessible without proper admin authentication
  3. Inspect MyCode configuration
    Check the 'mycode' table in the database for custom MyCode entries, or navigate to Admin CP > Configuration > MyCode to view any custom MyCode patterns that might be configured.
    Affected if Custom MyCode entries exist that could be exploited for information disclosure
  4. Check URL fetching configuration
    Examine the MyBB configuration settings (in 'settings' table) for any URL-related options, particularly 'allow_remote_images' or 'post_parser' settings that might enable external resource loading.
    Affected if Settings permit automatic fetching or parsing of external URLs through the MyCode system
  5. Audit admin user permissions
    Review the admin permissions in the 'adminusers' table or through Admin CP > Users > Admins to confirm which users have access to the MyCode management section.
    Affected if Any user account has administrator privileges that grant access to the Add Mycode function

Your environment is affected if you are running MyBB 1.8.38 AND the Add Mycode admin function is accessible to users without proper administrator authentication, or if custom MyCode configurations permit unauthorized information disclosure.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If the Add Mycode function should be restricted to authenticated administrators only, enforce proper authentication and authorization controls. If SSRF is involved, implement stricter URL validation and network segmentation to prevent internal resource disclosure.

Recommended fix Moderate confidence

MyBB 1.8.39 or latest 1.8.x stable release

  1. 1. Log in to your MyBB administration control panel
  2. 2. Navigate to the MyBB downloads page or official GitHub repository to check for newer versions
  3. 3. If MyBB 1.8.39 or later is available, download the latest stable release
  4. 4. Before upgrading, back up your database and all MyBB files
  5. 5. Upload the new version files, overwriting existing ones
  6. 6. Run the upgrade script by accessing your forum URL (e.g., https://yourforum.com/install/upgrade.php)
  7. 7. Clear all caches after upgrade completion
  8. 8. Verify the Mycode functionality works as expected post-upgrade
Caveat Standard upgrade within 1.8.x branch should not introduce breaking changes; always review release notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mybb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29460 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-29460 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data