CVE-2025-60039
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 rascals Noisa noisa allows Object Injection.This issue affects Noisa: from n/a through <= 2.6.0.
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 confidenceA deserialization of untrusted data vulnerability in the rascals Noisa package allows PHP Object Injection via the unserialize() function. This critical flaw (CVSS 9.8) can be exploited remotely without authentication, potentially enabling arbitrary code execution if suitable gadget chains exist 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
- 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.
-
Confirm Noisa is installedSearch for Noisa installation directories, check for noisa binaries, libraries, or services on the system. Common locations include /opt/noisa, /usr/local/noisa, or check system package managers.Affected if Noisa software is found on the system
-
Identify installed Noisa versionRun the version command for Noisa (typically 'noisa --version', 'noisa -v', or check a version file in the installation directory). Compare the version number to the affected range (up to and including 2.6.0).Affected if The installed version is 2.6.0 or any earlier version (e.g., 2.5.x, 2.4.x, etc.)
-
Verify deserialization feature is in useInspect application configuration files, source code, or runtime settings to determine if the deserialization module is enabled. Look for settings related to object deserialization, serialization handlers, or data processing pipelines.Affected if Deserialization functionality is enabled or configured in the Noisa environment
-
Check for untrusted data sourcesReview application logs, configuration, or network endpoints to identify if Noisa processes serialized data from external or untrusted sources. Check for deserialization endpoints that accept input from users, APIs, or network connections.Affected if Serialized data from untrusted or external sources can reach the Noisa deserialization functionality
-
Inspect input validation controlsExamine Noisa configuration files or application code for input validation, whitelist filtering, or sanitization measures around deserialization operations. Look for any existing security controls that may mitigate the vulnerability.Affected if No input validation or whitelist-based filtering is configured for deserialized data
The environment is affected if Noisa version 2.6.0 or earlier is installed AND the deserialization feature processes untrusted data without validation controls.
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 unserialize() calls with json_decode() or implement a strict allowlist of permitted classes using the second parameter of unserialize() in PHP 7+/8+. If a vendor patch is available, upgrade to the fixed version.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60039 — 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-60039 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