dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-58815

HIGH · 7.2 CVSS v3.1 Published 2025-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Deserialization of Untrusted Data vulnerability in Rubel Miah Aitasi Coming Soon aitasi-coming-soon allows Object Injection.This issue affects Aitasi Coming Soon: from n/a through <= 2.0.2.

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 · high confidence

PHP Object Injection vulnerability in the Aitasi Coming Soon WordPress plugin (versions <= 2.0.2) allows deserialization of untrusted data, potentially leading to code execution or other attacks via PHP magic methods in injected objects.

MitigationUpdate to the latest version of Aitasi Coming Soon plugin; if no patch is available, disable the plugin. Ensure no untrusted data is passed to PHP unserialize() functions within the plugin.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Aitasi Coming Soon plugin is installed
    Navigate to WordPress admin dashboard > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'aitaisa-coming-soon' or similar
    Affected if The plugin folder exists in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Aitasi Coming Soon > View Details, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The version is 2.0.2 or lower, or if no version is displayed and the plugin is present
  3. Determine if the plugin is active
    In WordPress admin > Plugins, check if Aitasi Coming Soon shows as 'Active'
    Affected if The plugin is active and running on the site
  4. Locate the vulnerable unserialize() call
    Inspect the main plugin PHP files for occurrences of 'unserialize()' function calls, particularly where user-supplied data (like $_GET, $_POST, $_COOKIE, or plugin settings) is passed as the argument
    Affected if The code contains an unserialize() call that processes untrusted input without prior validation
  5. Verify the attack surface is reachable
    Check if the plugin exposes any public-facing functionality (shortcodes, AJAX endpoints, frontend pages) that could trigger the unserialize() call with attacker-controlled data
    Affected if The unserialize() call can be reached via HTTP requests without authentication or with typical user-level access

If the Aitasi Coming Soon plugin version is 2.0.2 or lower and the plugin contains an unserialize() call processing untrusted input, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Aitasi Coming Soon plugin; if no patch is available, disable the plugin. Ensure no untrusted data is passed to PHP unserialize() functions within the plugin.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58815 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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