CVE-2026-24974
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeserialization of Untrusted Data vulnerability in NooTheme CitiLights noo-citilights allows Object Injection.This issue affects CitiLights: from n/a through <= 3.7.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePHP Object Injection vulnerability in NooTheme CitiLights theme via unsafe deserialization of untrusted data. The unserialize() function is being called on user-controlled input without proper validation, potentially allowing attackers to inject malicious PHP objects and execute arbitrary code through magic methods or gadget chains.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm CitiLights theme is installedCheck your WordPress themes directory for the CitiLights theme folder (typically wp-content/themes/cilights or similar). List the theme files to confirm presence.Affected if The CitiLights theme directory exists in the WordPress themes folder.
-
Locate unsafe unserialize() calls in theme filesSearch all PHP files within the theme directory for patterns like 'unserialize($_' to identify where deserialization occurs on user-supplied data.Affected if Any PHP file in the theme contains unserialize() called directly on $_POST, $_GET, $_REQUEST, or $_COOKIE variables.
-
Verify the input source is user-controllableExamine the code around the unserialize() call to determine if the data originates from HTTP request parameters, cookies, or other user-controllable sources without sanitization.Affected if The data passed to unserialize() comes directly from unauthenticated user input without validation.
-
Check for magic methods or gadget chain potentialReview the theme and active plugins for classes with magic methods (__wakeup, __destruct, __toString, etc.) that could be exploited for code execution if object injection is possible.Affected if The theme or its bundled plugins contain exploitable magic methods or known gadget chains.
You are affected if the CitiLights theme is installed and contains unserialize() being called on unvalidated user-controlled input, allowing PHP object injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace unsafe unserialize() calls with safer alternatives like json_decode() and implement strict input validation. If a patched version is available from the vendor, upgrade immediately. Audit for presence of exploitable gadget chains in the theme and installed plugins.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24974 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data