このページはまだあなたの言語に翻訳されていません。翻訳作業中のため、英語でコンテンツを表示しています。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2025-48827: RCE in vBulletin Forums
翻訳中…プラットフォーム
php
コンポーネント
vbulletin
修正版
6.0.4
CVE-2025-48827 is a critical Remote Code Execution (RCE) vulnerability discovered in vBulletin forums versions 5.0.0 through 5.7.5 and 6.0.0 through 6.0.3. The vulnerability allows unauthenticated attackers to execute arbitrary code on systems running these versions when using PHP 8.1 or later. A fix is available in version 6.0.4, and exploitation has been observed in the wild.
影響と攻撃シナリオ翻訳中…
This vulnerability poses a severe risk to vBulletin installations. An attacker can leverage the /api.php?method=protectedMethod pattern to bypass authentication and directly execute commands on the server. Successful exploitation could lead to complete system compromise, including data exfiltration, malware deployment, and denial of service. The unauthenticated nature of the exploit significantly broadens the attack surface, making it accessible to a wide range of threat actors. Given the popularity of vBulletin, a successful attack could impact numerous organizations and communities.
悪用の状況翻訳中…
This vulnerability is actively being exploited in the wild, as confirmed in May 2025. While specific threat actor attribution is not publicly available, the active exploitation underscores the urgency of patching. The vulnerability's ease of exploitation and the widespread use of vBulletin make it a high-priority target. The vulnerability was published on 2025-05-27. No KEV or EPSS score is currently available.
脅威インテリジェンス
エクスプロイト状況
EPSS
69.39% (99% パーセンタイル)
CISA SSVC
CVSS ベクトル
これらのメトリクスの意味は？
- Attack Vector
- ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
- Attack Complexity
- 低 — 特別な条件不要。安定して悪用可能。
- Privileges Required
- なし — 認証不要。資格情報なしで悪用可能。
- User Interaction
- なし — 自動かつ無音の攻撃。被害者は何もしない。
- Scope
- 変化あり — 攻撃が脆弱なコンポーネントを超えて他のシステムに波及可能。
- Confidentiality
- 高 — 機密性の完全喪失。全データが読み取り可能。
- Integrity
- 高 — 任意のデータの書き込み・変更・削除が可能。
- Availability
- 高 — 完全なクラッシュまたはリソース枯渇。完全なサービス拒否。
影響を受けるソフトウェア
弱点分類 (CWE)
タイムライン
- 予約済み
- 公開日
- EPSS 更新日
緩和策と回避策翻訳中…
The primary mitigation is to immediately upgrade vBulletin to version 6.0.4 or later. If upgrading is not immediately feasible, consider implementing temporary workarounds. These may include restricting access to the /api.php endpoint via a Web Application Firewall (WAF) or proxy server, specifically blocking requests with the method=protectedMethod parameter. Review and harden PHP configuration, ensuring proper access controls and disabling unnecessary features. Monitor vBulletin logs for suspicious activity, particularly requests to the /api.php endpoint.
修正方法翻訳中…
Actualice vBulletin a una versión posterior a 6.0.3. Si no es posible actualizar inmediatamente, considere deshabilitar temporalmente las funcionalidades API o implementar reglas de firewall para restringir el acceso a los endpoints API vulnerables hasta que se pueda realizar la actualización. Consulte el sitio web de vBulletin para obtener las últimas actualizaciones y parches de seguridad.
よくある質問翻訳中…
What is CVE-2025-48827 — RCE in vBulletin Forums?
CVE-2025-48827 is a critical Remote Code Execution vulnerability affecting vBulletin forums versions 5.0.0–6.0.3 running PHP 8.1+. It allows unauthenticated users to execute code on the server via the /api.php endpoint.
Am I affected by CVE-2025-48827 in vBulletin Forums?
You are affected if you are running vBulletin versions 5.0.0 through 5.7.5 or 6.0.0 through 6.0.3 and are using PHP 8.1 or later. Check your version immediately.
How do I fix CVE-2025-48827 in vBulletin Forums?
Upgrade vBulletin to version 6.0.4 or later. As a temporary workaround, restrict access to the /api.php endpoint using a WAF or proxy server.
Is CVE-2025-48827 being actively exploited?
Yes, CVE-2025-48827 is actively being exploited in the wild, making immediate patching essential.
Where can I find the official vBulletin advisory for CVE-2025-48827?
Refer to the official vBulletin security advisory for CVE-2025-48827 on the vBulletin website (check their security announcements section).
今すぐ試す — アカウント不要
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
依存関係ファイルをドラッグ＆ドロップ
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...