dbcve.org
VbulletinApplication

CVE-2025-48827

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-27
Fix available
A fix is available. Upgrade to after 6.0.3 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Public exploit Remotely reachable No privileges 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
vBulletin 5.0.0 through 5.7.5 and 6.0.0 through 6.0.3 allows unauthenticated users to invoke protected API controllers' methods when running on PHP 8.1 or later, as demonstrated by the /api.php?method=protectedMethod pattern, as exploited in the wild in May 2025.

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 · high confidence

vBulletin 5.0.0-5.7.5 and 6.0.0-6.0.3 contains an authentication bypass vulnerability where PHP 8.1+ introduces behavioral changes that allow unauthenticated attackers to invoke protected API controller methods via /api.php?method=protectedMethod, enabling potential remote code execution or data exfiltration.

MitigationUpgrade to the vendor-patched version immediately. As a temporary workaround, restrict access to api.php at the web server level or downgrade to PHP 8.0 or earlier until patching is complete.

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
VbulletinApplication
Affected:>= 5.0.0, <= 5.7.5>= 6.0.0, <= 6.0.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify PHP version is 8.1 or higher
    Run `php -v` or check via `phpinfo()` - look for the PHP 8.1.x or 8.2.x/8.3.x version string in the output
    Affected if PHP version is 8.1.0 or higher (vulnerability only affects PHP 8.1+)
  2. Check vBulletin version
    Check the version file typically at /includes/version.php or look for the version number in the admin control panel dashboard
    Affected if Version is 5.0.0 through 5.7.5 OR 6.0.0 through 6.0.3
  3. Confirm api.php exists and is accessible
    Check if the file /api.php exists in the web root and is accessible via HTTP (attempt a request to the URL)
    Affected if api.php exists and responds to requests (the attack surface)

User is affected if their vBulletin installation runs PHP 8.1+ AND the version is within 5.0.0-5.7.5 or 6.0.0-6.0.3 AND api.php is publicly accessible.

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
Upgrade available Upgrade to a release after 6.0.3
Interim mitigation

Upgrade to the vendor-patched version immediately. As a temporary workaround, restrict access to api.php at the web server level or downgrade to PHP 8.0 or earlier until patching is complete.

Recommended fix Moderate confidence

vBulletin 5.7.6 or later / 6.0.4 or later (check vendor for exact latest stable release)

  1. Check current vBulletin version by navigating to /admincp or checking the version file in the includes directory
  2. Verify the PHP version running on the server using phpinfo() or command line (php -v)
  3. If running PHP 8.1 or later on a vulnerable vBulletin version, immediately restrict API access via web server configuration (e.g., block or restrict access to /api.php to trusted IPs only)
  4. Check vBulletin's official download center (members.vbulletin.com) or vendor announcements for the latest security patch or version
  5. Download and install the latest vBulletin 5.7.x or 6.0.x version that includes the security fix
  6. After upgrading, verify the fix by attempting to access /api.php?method=protectedMethod as an unauthenticated user (should return an error or require authentication)
  7. Review server logs for any signs of exploitation attempts from May 2025
Caveat Review vBulletin upgrade documentation for potential template/customization breaking changes between minor versions; test in staging environment before production deployment

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

Fix this in Vbulletin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48827 — 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-48827 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