dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-52827

HIGH · 8.8 CVSS v3.1 Published 2025-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 uxper Nuss nuss allows Object Injection.This issue affects Nuss: from n/a through <= 1.3.3.

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 confidence

The nuss package versions through 1.3.3 contain a deserialization vulnerability allowing object injection. This type of flaw occurs when untrusted data is deserialized without proper validation, potentially enabling attackers to instantiate malicious objects, execute arbitrary code, or perform other attacks depending on the application's object classes.

MitigationUpgrade to the latest version when a patch becomes available. Until then, validate all input before deserialization, implement whitelist-based object instantiation, and consider using safer serialization formats like JSON instead of PHP object serialization.

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 checks

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

  1. Locate the nuss package installation
    Run 'composer show nuss' or check your composer.json dependencies for 'nuss'
    Affected if The package is not listed in your dependencies
  2. Determine the installed nuss version
    Run 'composer show nuss --direct' to see the exact version number installed
    Affected if The version is 1.3.3 or any earlier version (1.x.x <= 1.3.3)
  3. Identify deserialization usage in your codebase
    Search your application code for calls to PHP unserialize(), json_decode() with object injection, or similar deserialization functions
    Affected if Your code deserializes data that originates from user input or external sources without validation
  4. Check if nuss handles serialized data
    Review any code that passes data through nuss functions or classes to determine if untrusted input reaches deserialization routines
    Affected if Your application passes untrusted serialized data through nuss functionality

You are affected if the nuss package version is 1.3.3 or lower AND your application deserializes untrusted data using PHP's unserialize or similar functions.

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

Upgrade to the latest version when a patch becomes available. Until then, validate all input before deserialization, implement whitelist-based object instantiation, and consider using safer serialization formats like JSON instead of PHP object serialization.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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