このページはまだあなたの言語に翻訳されていません。翻訳作業中のため、英語でコンテンツを表示しています。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-39639: Unauthorized Access in RPS Include Content
プラットフォーム
wordpress
コンポーネント
rps-include-content
CVE-2026-39639 describes an unauthorized access vulnerability within the RPS Include Content plugin for WordPress. This flaw allows authenticated users with contributor-level access or higher to execute actions they shouldn't be able to. The vulnerability impacts versions of the plugin up to and including 1.2.2, and a fix is available in later versions.
このCVEがあなたのプロジェクトに影響するか確認
依存関係ファイルをアップロードすれば、このCVEや他のCVEがあなたに影響するか即座にわかります。
影響と攻撃シナリオ翻訳中…
The primary impact of CVE-2026-39639 is the potential for unauthorized actions within a WordPress site. An attacker, already logged in with a contributor account (or higher), can leverage this missing capability check to bypass access controls and perform actions typically restricted to administrators or other privileged roles. This could include modifying content, installing plugins, or altering site settings, leading to data compromise, defacement, or even complete site takeover. The blast radius is limited to the scope of actions the contributor account can perform, but the potential for damage is still significant.
悪用の状況翻訳中…
CVE-2026-39639 was published on 2026-02-14. Its severity is currently assessed as medium. No public proof-of-concept exploits are currently known. The vulnerability is not listed on KEV or EPSS, indicating a low to medium probability of exploitation. Monitor WordPress security forums and vulnerability databases for any updates.
脅威インテリジェンス
エクスプロイト状況
EPSS
0.03% (8% パーセンタイル)
CVSS ベクトル
これらのメトリクスの意味は？
- Attack Vector
- ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
- Attack Complexity
- 低 — 特別な条件不要。安定して悪用可能。
- Privileges Required
- 低 — 有効なユーザーアカウントがあれば十分。
- User Interaction
- なし — 自動かつ無音の攻撃。被害者は何もしない。
- Scope
- 変化なし — 影響は脆弱なコンポーネントのみ。
- Confidentiality
- なし — 機密性への影響なし。
- Integrity
- 低 — 限定的な範囲でデータ変更可能。
- Availability
- なし — 可用性への影響なし。
影響を受けるソフトウェア
弱点分類 (CWE)
タイムライン
- 予約済み
- 公開日
- 更新日
- EPSS 更新日
緩和策と回避策翻訳中…
The primary mitigation for CVE-2026-39639 is to upgrade the RPS Include Content plugin to a version that includes the necessary capability checks. If upgrading immediately is not possible due to compatibility issues or breaking changes, consider restricting contributor access to minimize the potential impact. While a direct WAF rule is unlikely to be effective, carefully reviewing and restricting plugin permissions within WordPress can help reduce the attack surface. After upgrading, verify the fix by attempting to perform an action that would normally require administrator privileges while logged in as a contributor.
修正方法
既知の修正パッチはありません。脆弱性の詳細を詳細に検討し、組織のリスク許容度に基づいて軽減策を講じてください。影響を受けるソフトウェアをアンインストールし、代替手段を見つけるのが最善かもしれません。
よくある質問翻訳中…
What is CVE-2026-39639 — Unauthorized Access in RPS Include Content?
CVE-2026-39639 is a medium severity vulnerability affecting the RPS Include Content WordPress plugin up to version 1.2.2. It allows authenticated contributors to perform unauthorized actions due to a missing capability check.
Am I affected by CVE-2026-39639 in RPS Include Content?
You are affected if you are using the RPS Include Content plugin in WordPress versions 1.2.2 or earlier. Check your plugin version immediately.
How do I fix CVE-2026-39639 in RPS Include Content?
Upgrade the RPS Include Content plugin to the latest available version, which includes the necessary capability checks to prevent unauthorized access.
Is CVE-2026-39639 being actively exploited?
Currently, there are no known public exploits or active campaigns targeting CVE-2026-39639, but it's crucial to apply the patch proactively.
Where can I find the official RPS Include Content advisory for CVE-2026-39639?
Refer to the official RPS Include Content plugin documentation or the WordPress plugin repository for updates and security advisories related to CVE-2026-39639.
この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...