CVE-2026-28105
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 ThemeREX Good Energy goodenergy allows Object Injection.This issue affects Good Energy: from n/a through <= 1.7.7.
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 ThemeREX Good Energy WordPress theme (versions <= 1.7.7) where untrusted user input is passed to PHP's unserialize() function, potentially allowing remote code execution through malicious serialized objects.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify if Good Energy theme is installedCheck the WordPress themes directory (wp-content/themes/) for a folder named 'good-energy' or similar ThemeREX theme folder. List installed themes via WP CLI: wp theme list --status=activeAffected if The Good Energy theme folder exists in the WordPress themes directory
-
Determine installed theme versionOpen the theme's style.css file in wp-content/themes/good-energy/ and locate the 'Version:' header in the CSS comment block at the top. Alternatively, check functions.php for a version constant.Affected if The version displayed is 1.7.7 or lower
-
Locate unserialize() calls in theme filesSearch PHP files in the theme directory for 'unserialize' using grep: grep -r "unserialize" wp-content/themes/good-energy/ or WP CLI: wp search-replace "unserialize" --dry-run --include="*.php" --base=wp-content/themes/good-energy/Affected if Any theme PHP files contain unserialize() function calls
-
Verify user input reaches unserialize()Examine the PHP files containing unserialize() calls. Look for $_GET, $_POST, $_REQUEST, or other user-supplied data passed as the unserialize() argument. Check if the data flows from HTTP request parameters to the deserialization function.Affected if User-controllable input (request parameters, cookies, or similar) is passed directly to unserialize() without validation
-
Check if vulnerable feature is accessibleDetermine whether the code path containing the vulnerable unserialize() call is reachable. Test if the relevant page, admin panel section, or AJAX endpoint is accessible to untrusted users (not only administrators).Affected if The unserialize() code path is accessible to authenticated users with low privileges or unauthenticated visitors
Your environment is affected if the Good Energy theme (version 1.7.7 or lower) is installed and contains unserialize() calls that process user-supplied input without validation.
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 dataUpdate Good Energy theme to a patched version; alternatively, replace unserialize() calls with json_decode() and implement proper input validation/sanitization on any user-supplied data before deserialization.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28105 — 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-28105 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