此页面尚未翻译为您的语言。我们正在努力翻译,目前显示英文内容。
💡 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项目 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...