CVE-2026-4608: SQL Injection in ProfileGrid WordPress Plugin
平台
wordpress
组件
profilegrid-user-profiles-groups-and-communities
修复版本
5.9.8.5
CVE-2026-4608 describes a blind SQL Injection vulnerability discovered in the ProfileGrid WordPress plugin, a tool for user profiles, groups, and communities. This flaw allows authenticated attackers, even those with Subscriber-level access, to inject malicious SQL queries. The vulnerability impacts versions up to 5.9.8.4, and a patch is available in version 5.9.8.5.
检测此 CVE 是否影响你的项目
上传你的依赖文件,立即了解此CVE和其他CVE是否影响你。
影响与攻击场景翻译中…
An attacker exploiting this SQL Injection vulnerability can potentially extract sensitive information stored within the WordPress database. While the vulnerability requires authentication (Subscriber level or higher), the ease of access makes it a significant risk. Successful exploitation could lead to the theft of user credentials, personal data, configuration details, or even database schema information. The impact is amplified if the database contains sensitive data like financial information or personally identifiable information (PII). This vulnerability shares similarities with other SQL Injection attacks where attackers can bypass security controls and gain unauthorized access to data.
利用背景翻译中…
CVE-2026-4608 was published on May 13, 2026. The vulnerability’s severity is currently assessed as medium. There is no indication of this CVE being listed on KEV or having an EPSS score. Public Proof-of-Concept (POC) exploits are currently unknown, but the ease of exploitation makes it a potential target for opportunistic attackers. Monitor WordPress plugin directories and security forums for any emerging exploitation attempts.
威胁情报
漏洞利用状态
CISA SSVC
CVSS 向量
这些指标意味着什么?
- Attack Vector
- 网络 — 可通过互联网远程利用,无需物理或本地访问。攻击面最大。
- Attack Complexity
- 低 — 无需特殊条件,可以稳定地利用漏洞。
- Privileges Required
- 低 — 任何有效用户账户均可。
- User Interaction
- 无 — 攻击自动且无声,受害者无需任何操作。
- Scope
- 未改变 — 影响仅限于脆弱组件本身。
- Confidentiality
- 高 — 完全丧失机密性,攻击者可读取所有数据。
- Integrity
- 无 — 无完整性影响。
- Availability
- 无 — 无可用性影响。
受影响的软件
弱点分类 (CWE)
时间线
- 已保留
- 发布日期
- 修改日期
缓解措施和替代方案翻译中…
The primary mitigation for CVE-2026-4608 is to immediately upgrade the ProfileGrid plugin to version 5.9.8.5 or later. If upgrading is not immediately feasible due to compatibility issues or breaking changes, consider implementing a Web Application Firewall (WAF) rule to filter out suspicious SQL queries targeting the 'rid' parameter. Specifically, look for unusual characters or SQL keywords within the parameter value. Additionally, review and harden database user permissions to limit the potential damage from a successful SQL Injection attack. After upgrading, confirm the fix by attempting a SQL Injection attack on the 'rid' parameter and verifying that it is properly sanitized.
修复方法
更新到 5.9.8.5 版本,或更新的补丁版本
常见问题翻译中…
What is CVE-2026-4608 — SQL Injection in ProfileGrid WordPress Plugin?
CVE-2026-4608 is a medium severity SQL Injection vulnerability affecting the ProfileGrid WordPress plugin versions 0–5.9.8.4, allowing authenticated attackers to extract sensitive data.
Am I affected by CVE-2026-4608 in ProfileGrid WordPress Plugin?
If you are using ProfileGrid WordPress plugin versions 0 through 5.9.8.4, you are potentially affected by this vulnerability. Upgrade immediately.
How do I fix CVE-2026-4608 in ProfileGrid WordPress Plugin?
Upgrade the ProfileGrid plugin to version 5.9.8.5 or later. If immediate upgrade is not possible, implement WAF rules to filter suspicious SQL queries.
Is CVE-2026-4608 being actively exploited?
There are currently no known active campaigns exploiting CVE-2026-4608, but the ease of exploitation makes it a potential target.
Where can I find the official ProfileGrid advisory for CVE-2026-4608?
Refer to the ProfileGrid website and WordPress plugin repository for the official advisory and update information.
检测此 CVE 是否影响你的项目
上传你的依赖文件,立即了解此CVE和其他CVE是否影响你。
立即扫描您的WordPress项目 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...