dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-3590

MEDIUM · 6.3 CVSS v3.1 Published 2025-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
A vulnerability has been found in Adianti Framework up to 8.0 and classified as critical. Affected by this vulnerability is an unknown functionality. The manipulation leads to deserialization. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 8.1 is able to address this issue. It is recommended to upgrade the affected component.

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

A deserialization vulnerability exists in Adianti Framework versions up to 8.0, allowing remote attackers to manipulate serialized PHP objects. The flaw is exploitable remotely and a public exploit is available, potentially enabling code execution or other deserialization attacks.

MitigationUpgrade Adianti Framework from any version up to 8.0 to version 8.1 to address the deserialization vulnerability.

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
Low
Integrity
Low
Availability
Low

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

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 Adianti Framework installation
    Search for Adianti-related files or directories in the web root, such as 'adianti' folders, 'Framework.php', or 'Adianti' namespace references in PHP files.
    Affected if Adianti Framework files are found in the environment.
  2. Determine installed version
    Locate version information in composer.json, a VERSION file, or within core framework PHP files that define the version constant. Compare the version string to the affected range (8.0 and below).
    Affected if The installed version is 8.0 or lower.
  3. Check for deserialization endpoints
    Search for PHP files that handle unserialize() calls, particularly in controller or service files that process user input. Look for patterns like 'unserialize($_POST' or 'unserialize($_GET' in the codebase.
    Affected if Code contains unserialize() calls that process untrusted input without validation.
  4. Inspect PHP object handling configuration
    Review php.ini or application configuration files for object serialization settings, and check if any custom autoloader or wrapper classes handle PHP object deserialization.
    Affected if Custom serialization handlers or unserialize-based functionality is enabled or exposed.

If Adianti Framework version 8.0 or lower is installed and the application uses unserialize() on untrusted input, the environment is likely affected by CVE-2025-3590.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Adianti Framework from any version up to 8.0 to version 8.1 to address the deserialization vulnerability.

Recommended fix Moderate confidence

8.1

  1. 1. Back up the current Adianti Framework application and database before proceeding with any upgrade
  2. 2. Identify the current Adianti Framework version in use (check composer.json or version file)
  3. 3. Download Adianti Framework version 8.1 from the official source or update via Composer
  4. 4. Replace the existing framework files with the new version 8.1 files
  5. 5. Run any database migrations if provided with the update
  6. 6. Test the application thoroughly in a staging environment to verify functionality
  7. 7. Deploy the upgraded version to production
Caveat Review Adianti Framework 8.1 release notes for any breaking changes or deprecated features before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3590 — 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-3590 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