CVE-2026-24977
Blind SQL Injection in NooTheme Organici Library
Publication date: 2026-03-25
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nootheme | organici_library | to 2.1.2 (inc) |
| nootheme | noo-organici-library | to 2.1.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL Injection vulnerability in the NooTheme Organici Library Plugin allows attackers to interact directly with the plugin's database, potentially leading to data theft or manipulation.
Such unauthorized access and data compromise can lead to violations of data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and breaches.
Failure to patch this vulnerability promptly could result in non-compliance with these standards due to the increased risk of data breaches.
Can you explain this vulnerability to me?
CVE-2026-24977 is a high-priority SQL Injection vulnerability found in the WordPress Organici Library Plugin versions up to 2.1.2. This vulnerability allows attackers with subscriber or developer privileges to exploit the plugin by injecting malicious SQL commands. This can enable them to interact directly with the plugin's database without proper authorization.
The issue is classified under the OWASP Top 10 category A3: Injection, indicating it is a critical security flaw related to improper neutralization of special elements in SQL commands.
How can this vulnerability impact me? :
This vulnerability can have serious impacts including unauthorized data theft or manipulation within the plugin's database. Attackers exploiting this flaw can compromise the integrity and confidentiality of your data.
Because the vulnerability requires only subscriber or developer privileges to exploit, it can be leveraged in mass campaigns targeting many websites, regardless of their traffic or popularity.
If exploited, it could lead to loss of sensitive information, unauthorized changes to data, and potentially further compromise of the affected website.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a Blind SQL Injection in the WordPress Organici Library Plugin up to version 2.1.2, which allows attackers with subscriber or developer privileges to interact with the database.
Detection can involve monitoring for unusual database queries or suspicious HTTP requests targeting the plugin endpoints that may contain SQL injection payloads.
While specific commands are not provided, typical detection methods include using web application firewalls (WAF) with rules targeting SQL injection patterns or analyzing web server logs for suspicious input patterns.
- Use tools like sqlmap to test for SQL injection vulnerabilities against the plugin endpoints.
- Check web server logs for unusual query parameters or POST data containing SQL syntax such as ' OR '1'='1 or UNION SELECT.
- Enable and review logs from security plugins or WAFs that may detect or block SQL injection attempts.
What immediate steps should I take to mitigate this vulnerability?
The primary and immediate mitigation step is to update the WordPress Organici Library Plugin to version 2.1.3 or later, where the vulnerability has been patched.
Until the update can be applied, it is recommended to enable mitigation rules provided by Patchstack that block attacks targeting this vulnerability.
Additionally, enabling auto-updates for vulnerable plugins can help ensure rapid protection against exploitation.