このページはまだあなたの言語に翻訳されていません。翻訳作業中のため、英語でコンテンツを表示しています。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-6512: Authorization Bypass in InfusedWoo Pro
プラットフォーム
wordpress
コンポーネント
infusedwooPRO
修正版
5.1.3
CVE-2026-6512 represents a critical authorization bypass vulnerability affecting the InfusedWoo Pro plugin for WordPress. This flaw allows unauthenticated attackers to perform destructive actions, including permanent deletion of critical data and modification of post statuses. The vulnerability impacts versions 0.0.0 through 5.1.2, and a patch is available in version 5.1.3.
このCVEがあなたのプロジェクトに影響するか確認
依存関係ファイルをアップロードすれば、このCVEや他のCVEがあなたに影響するか即座にわかります。
影響と攻撃シナリオ翻訳中…
The impact of this vulnerability is severe due to the ease of exploitation and the potential for widespread data loss. An attacker can leverage this bypass to permanently delete posts, pages, products, and orders, effectively crippling an e-commerce site. The ability to mass-delete comments on any post can damage a site's reputation and user engagement. Furthermore, attackers can modify post statuses, potentially disrupting content publishing workflows and creating misleading information for users. This vulnerability's simplicity makes it a high-priority target for malicious actors.
悪用の状況翻訳中…
CVE-2026-6512 was published on 2026-05-14. Currently, there are no publicly known active campaigns exploiting this vulnerability. The ease of exploitation, coupled with the plugin's popularity, suggests it could become a target. No KEV or EPSS score is currently available. Monitor security advisories and threat intelligence feeds for any indications of exploitation.
脅威インテリジェンス
エクスプロイト状況
CISA SSVC
CVSS ベクトル
これらのメトリクスの意味は?
- Attack Vector
- ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
- Attack Complexity
- 低 — 特別な条件不要。安定して悪用可能。
- Privileges Required
- なし — 認証不要。資格情報なしで悪用可能。
- User Interaction
- なし — 自動かつ無音の攻撃。被害者は何もしない。
- Scope
- 変化なし — 影響は脆弱なコンポーネントのみ。
- Confidentiality
- 高 — 機密性の完全喪失。全データが読み取り可能。
- Integrity
- 高 — 任意のデータの書き込み・変更・削除が可能。
- Availability
- なし — 可用性への影響なし。
影響を受けるソフトウェア
弱点分類 (CWE)
タイムライン
- 予約済み
- 公開日
緩和策と回避策翻訳中…
The primary mitigation is to immediately upgrade the InfusedWoo Pro plugin to version 5.1.3 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider temporarily restricting access to the plugin's administrative functions. Implement strict user role permissions within WordPress to limit the potential damage an attacker could inflict if they gain unauthorized access. While a WAF cannot directly prevent this authorization bypass, it can help detect and block suspicious requests attempting to exploit it. After upgrading, verify the fix by attempting to access plugin functions without proper authentication; successful access indicates the vulnerability persists.
修正方法
バージョン5.1.3、またはそれ以降の修正バージョンにアップデートしてください
よくある質問翻訳中…
What is CVE-2026-6512 — Authorization Bypass in InfusedWoo Pro?
CVE-2026-6512 is a critical authorization bypass vulnerability in the InfusedWoo Pro WordPress plugin, allowing unauthenticated attackers to delete data and modify post statuses. It affects versions 0.0.0 through 5.1.2.
Am I affected by CVE-2026-6512 in InfusedWoo Pro?
You are affected if you are using InfusedWoo Pro version 0.0.0 through 5.1.2. Check your plugin version and upgrade immediately if necessary.
How do I fix CVE-2026-6512 in InfusedWoo Pro?
Upgrade InfusedWoo Pro to version 5.1.3 or later to resolve this vulnerability. If immediate upgrade is not possible, restrict access to plugin administrative functions.
Is CVE-2026-6512 being actively exploited?
Currently, there are no publicly known active campaigns exploiting CVE-2026-6512, but its ease of exploitation makes it a potential target.
Where can I find the official InfusedWoo Pro advisory for CVE-2026-6512?
Refer to the official InfusedWoo Pro website or WordPress plugin repository for the latest advisory and update information regarding CVE-2026-6512.
このCVEがあなたのプロジェクトに影響するか確認
依存関係ファイルをアップロードすれば、このCVEや他のCVEがあなたに影響するか即座にわかります。
WordPressプロジェクトを今すぐスキャン — アカウント不要
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...