LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24976: WordPress Organici Library plugin <= 2.1.2 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in NooTheme Organici Library noo-organici-library allows Object Injection.This issue affects Organici Library: from n/a through <= 2.1.2.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-24976 affects the WordPress Organici Library plugin from NooTheme through version 2.1.2. It is a high-severity unsafe deserialization issue that can allow PHP object injection. A logged-in attacker could potentially impact confidentiality, integrity, and availability. No active exploitation is stated in the provided sources.

Executive priority

Treat as a high-priority WordPress plugin issue if the organization uses Organici Library. Prioritize internet-facing sites, sites allowing user registration, and business-critical WordPress properties. If the plugin is absent, no direct action is indicated beyond routine monitoring.

Technical view

The issue is CWE-502, deserialization of untrusted data, in noo-organici-library. CVSS 3.1 is 8.8: network-accessible, low complexity, low privileges required, no user interaction, with high confidentiality, integrity, and availability impact. The CVE record lists Organici Library versions through 2.1.2 as affected.

Likely exposure

Exposure is likely limited to WordPress sites that have the NooTheme Organici Library plugin installed at version 2.1.2 or earlier. The CVSS vector indicates exploitation requires low privileges, so public registration or weak account governance may increase practical risk.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. The risk is still significant because the flaw is network-reachable, low-complexity, requires no user interaction, and may affect all three major security outcomes if exploitable in a target environment.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE classification, and Patchstack database reference. The sources identify the vulnerability class and affected version range but do not provide exploit details, proof of active exploitation, or a named fixed version in the supplied bundle.

Mitigation direction

  • Inventory WordPress sites for the noo-organici-library plugin.
  • Identify installations running Organici Library version 2.1.2 or earlier.
  • Check NooTheme and Patchstack guidance for a fixed release or official mitigation.
  • If no fix is available, evaluate disabling or removing the plugin.
  • Reduce unnecessary WordPress user accounts and privileges where feasible.

Validation and detection

  • Confirm plugin presence and version on each WordPress instance.
  • Compare installed versions against the affected range: through 2.1.2.
  • Review vendor and Patchstack pages for updated remediation status.
  • Check WordPress user registration and role exposure.
  • Review relevant web and application logs for suspicious authenticated activity.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24976 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-24976Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NooThemeOrganici Librarynoo-organici-library, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.