CVE-2025-58662
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 awesomesupport Awesome Support awesome-support allows Object Injection.This issue affects Awesome Support: from n/a through <= 6.3.5.
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 confidenceThis is a PHP Object Injection vulnerability in the Awesome Support WordPress plugin. The plugin deserializes untrusted data without proper validation, which could allow an attacker to manipulate PHP objects and potentially execute arbitrary code through available gadget chains in the application environment.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Awesome Support plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Awesome Support' in the list of active plugins.Affected if The Awesome Support plugin appears in the installed plugins list, regardless of activation status
-
Identify the installed plugin versionIn the WordPress admin under Plugins > Installed Plugins, click on the Awesome Support plugin to view its details, or inspect the main plugin file (usually awesome-support.php) and look for the version comment/header.Affected if The plugin is installed and a version number is displayed
-
Compare version against the patched releaseTake the installed version number identified in the previous step and compare it to the fixed version 6.3.6. Versions below 6.3.6 are considered vulnerable.Affected if The installed version is lower than 6.3.6 (for example, 6.3.5, 6.3.0, or any 6.x.x version below 6.3.6)
-
Verify if the plugin handles serialized dataIf you have file system access, examine the plugin directory for PHP files containing unserialize() function calls, particularly those processing user-supplied input such as form data, API requests, or stored options.Affected if The plugin code contains unserialize() calls that process external or untrusted data
A WordPress site is affected if the Awesome Support plugin is installed with a version lower than 6.3.6 and the plugin processes serialized data from untrusted sources.
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 deserialization (unserialize()) with safer alternatives like JSON decoding, implement strict input validation, and update to a patched version (6.3.6 or higher) when released. If immediate patching is not possible, consider disabling the affected functionality.
- 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-2025-58662 — 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-2025-58662 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