CVE-2021-26613
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 · uneditedimproper input validation vulnerability in nexacro permits copying file to the startup folder using rename method.
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 confidenceImproper input validation in nexacro's file rename method allows copying files to the Windows startup folder, enabling an attacker to achieve persistence or privilege escalation by placing malicious executables in an auto-start location.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 17.0, < 17.1.2.500CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify Nexacro installationSearch for Nexacro-related executables or libraries (nexacro*.exe, nexacro*.dll) in common program directories or the application bin folder. Check registry keys under HKLM\SOFTWARE\Tobesoft or HKCU\SOFTWARE\Tobesoft for installed Nexacro components.Affected if Tobesoft Nexacro is found on the system
-
Determine installed Nexacro versionLocate the Nexacro runtime DLL or executable and check its version property (right-click > Properties > Details). Common paths include Program Files\Tobesoft\Nexacro or the application's own bin directory.Affected if Version is >= 17.0 and < 17.1.2.500
-
Inspect application file operationsMonitor or review application logs, code, or configuration for usage of file rename or copy methods provided by the Nexacro platform API (such as File.copy or File.rename functions in Nexacro script).Affected if The application uses Nexacro file rename/copy methods with user-controllable input
-
Check for unauthorized startup entriesExamine the Windows startup folder locations: %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup and %PROGRAMDATA%\Microsoft\Windows\Start Menu\Programs\Startup. Look for unfamiliar executables recently placed there.Affected if Suspicious executables exist in startup folders that correspond to files accessible via the vulnerable rename method
-
Verify file operation permissionsReview if the Nexacro application runtime has write permissions to system directories outside the application sandbox, particularly the user or common startup folders.Affected if The application process can write to Windows startup directories
A system is affected if Tobesoft Nexacro version 17.0 through 17.1.2.499 is installed and the application uses file rename/copy operations that could be manipulated to place files in the Windows startup folder.
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 · scoped17.1.2.500
Implement strict input validation on file paths and names in the rename/copy function, restricting operations to allowed directories and preventing traversal to system folders like the startup folder.
17.1.2.500 or later
- Upgrade Nexacro to version 17.1.2.500 or later to resolve the improper input validation vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26613 — 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-2021-26613 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