CVE-2025-5952
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 · uneditedA vulnerability, which was classified as critical, has been found in Zend.To up to 6.10-6 Beta. This issue affects the function exec of the file NSSDropoff.php. The manipulation of the argument file_1 leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 6.10-7 is able to address this issue. It is recommended to upgrade the affected component. This affects a rather old version of the software. The vendor recommends updating to the latest release. Additional countermeasures have been added in 6.15-8.
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 confidenceOS command injection vulnerability in Zend.To NSSDropoff.php where the file_1 argument is passed unsanitized to the exec() function, allowing remote attackers to execute arbitrary OS commands.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the NSSDropoff.php fileSearch the web server filesystem for NSSDropoff.php within the Zend.To installation directory (commonly in library/Zend/To/ or similar paths)Affected if The file does not exist (Zend.To not installed or different component structure)
-
Determine Zend.To versionCheck version.php, composer.json, or any version metadata file in the Zend.To installation rootAffected if Version is present and is earlier than 6.10-7 (or cannot be determined and the code pattern matches the vulnerability)
-
Inspect NSSDropoff.php for exec() call with file_1Open NSSDropoff.php and search for 'exec(' or 'shell_exec(' functions. Locate the line where the file_1 parameter is passed to exec() without visible sanitization (such as escapeshellarg() or preg_replace)Affected if The code contains an exec() call that incorporates the file_1 parameter directly without sanitization functions
-
Verify the vulnerable parameter is user-controllableCheck if the file_1 parameter is received from user input (such as $_POST, $_GET, or similar request data) and passed to the exec() callAffected if The file_1 parameter flows from user input directly into the exec() function without validation
Affected if Zend.To is installed with version earlier than 6.10-7 AND the NSSDropoff.php file contains an exec() call using the file_1 parameter without sanitization.
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.
dbcve · scopedUpgrade to version 6.10-7 or later (vendor recommends 6.15-8 for complete remediation). If immediate upgrade is not feasible, input validation/sanitization on the file_1 parameter or removal of the vulnerable exec call is required.
6.10-7 (vendor recommends latest release 6.15-8 for complete security fixes)
- 1. Identify the current version of Zend.To by checking the application or configuration files
- 2. Obtain the upgrade package for Zend.To version 6.10-7 or later (vendor recommends latest release 6.15-8 for complete fixes)
- 3. Backup the current installation and database before proceeding with the upgrade
- 4. Apply the upgrade following the vendor's documented upgrade procedure
- 5. Verify the upgrade was successful by checking the new version number
- 6. Test that the NSSDropoff.php functionality works correctly after the upgrade
- 7. Confirm the command injection vulnerability is resolved by verifying the exec function no longer accepts unsanitized input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5952 — 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-5952 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