Wisconsin Engraving Company, Inc. Step 4: ticket instructions, client email (paste share links after export), Sales quote ticket, remaining remediations, and Manage PSA notes.
Scan: 2026-10-12 | Presenter: Chris Knospe | Export set: Top 15 | Client type: RMIT/CMIT
The following vulnerabilities/remediations are NOT considered standard maintenance and therefore need to be quoted. Remediation(s): -------------------------------------------------------------------------------------------- Vulnerability: Windows 10 (all versions) Remediation Options: Update to version 5.7.2 or later; uninstall if not in use Target Machines: ENG22.weco (cad), DESKTOP-SL7Q6OT.weco (jcarlson), sales3.weco (nlatz), eng19.weco (cad), eng20.weco (dwnuk), office2.weco (cad), eng06.weco (emarek) Estimated Time of Remediation: 2 hours Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Windows Server 2012 (all versions) Remediation Options: Replace or upgrade the listed systems, then retire the current asset Target Machines: WESHARE, weacct.weco, wepdc.weco (rradmin) Estimated Time of Remediation: 1 hour Remediation Method: Quote the replacement or upgrade, then coordinate the change with the client. Verify the new build after cutover. -------------------------------------------------------------------------------------------- Vulnerability: Windows 11 (all versions) Remediation Options: Install the listed Windows updates, or decommission the host if it is not in use Target Machines: RECEPTION.weco Estimated Time of Remediation: 1 hour Remediation Method: Apply the listed updates via RMM or Windows Update. Verify the build after reboot. -------------------------------------------------------------------------------------------- Vulnerability: Apache HTTP Server Remediation Options: Update to version 2.4.67 or later; uninstall if not in use Target Machines: eng06.weco (emarek) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: GPL Ghostscript Remediation Options: Update to version 10.08.0 or later; uninstall if not in use Target Machines: eng20.weco (dwnuk) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: fortios Remediation Options: Update firmware to the current vendor release, or replace the device if it is out of support Target Machines: WisconsinEngraving60F Estimated Time of Remediation: 1 hour Remediation Method: Update firmware from the vendor during a maintenance window. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Tenable Nessus (x64) Remediation Options: Update to version 10.12.5 or later; uninstall if not in use Target Machines: wepdc.weco (rradmin) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Microsoft Teams Remediation Options: Update to version 26260.1701.5139.3736 or later; uninstall if not in use Target Machines: wiseng-dt-25-01.weco (lhenn), office2.weco (cad), eng06.weco (emarek), sales3.weco (nlatz), DESKTOP-SL7Q6OT.weco (jcarlson), FrontDesk-PC.weco (customerservice) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: Firebird/InterBase(r) ODBC driver Remediation Options: Update to version 3.0.10 or later; uninstall if not in use Target Machines: eng06.weco (emarek), eng20.weco (dwnuk) Estimated Time of Remediation: 1 hour Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinVerifyTrust Signature Validation Vulnerability Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: DESKTOP-SL7Q6OT.weco (jcarlson), eng06.weco (emarek), eng19.weco (cad), eng20.weco (dwnuk), ENG22.weco (cad), office2.weco (cad), PETES-OFFICE.weco (pkambouris), sales3.weco (nlatz), sales4.weco (tstapleton), SOLIDWORKS.weco (cad), weacct.weco, wepdc.weco (rradmin), WESHARE, wiseng-dt-25-01.weco (lhenn) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: Speculative Store Bypass Remediation Options: Correct the listed configuration, or leave it when the client accepts the risk Target Machines: DESKTOP-SL7Q6OT.weco (jcarlson), eng06.weco (emarek), eng19.weco (cad), eng20.weco (dwnuk), ENG22.weco (cad), FrontDesk-PC.weco (customerservice), office2.weco (cad), PETES-OFFICE.weco (pkambouris), RECEPTION.weco, sales3.weco (nlatz), sales4.weco (tstapleton), SOLIDWORKS.weco (cad), wiseng-dt-25-01.weco (lhenn) Estimated Time of Remediation: 1 hour Remediation Method: Apply the configuration change after confirming impact. Verify the setting after the change. -------------------------------------------------------------------------------------------- Vulnerability: powershellv2 Remediation Options: Update to the current version; uninstall if not in use Target Machines: eng06.weco (emarek), eng19.weco (cad), eng20.weco (dwnuk), ENG22.weco (cad), FrontDesk-PC.weco (customerservice), office2.weco (cad), RECEPTION.weco, sales3.weco (nlatz), SOLIDWORKS.weco (cad), weacct.weco, wepdc.weco (rradmin), WESHARE Estimated Time of Remediation: 2 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: WinRAR 7.13 (64-bit) Remediation Options: Update to version 7.23 or later; uninstall if not in use Target Machines: SOLIDWORKS.weco (cad), eng19.weco (cad) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: 7-Zip 26.03 (x64 edition) Remediation Options: Update to version 26.04 or later; uninstall if not in use Target Machines: RECEPTION.weco Estimated Time of Remediation: 0.5 hours Remediation Method: RMM patching, or ScreenConnect Backstage install of latest version over existing. Verify version after update. -------------------------------------------------------------------------------------------- Vulnerability: FileZilla Client Remediation Options: Update to version 3.71.1 or later; uninstall if not in use Target Machines: SOLIDWORKS.weco (cad) Estimated Time of Remediation: 0.5 hours Remediation Method: RMM software deployment, ScreenConnect Backstage silent install as fallback. Verify version after update. -------------------------------------------------------------------------------------------- Total Estimated Time: 14.5 hours
Steps performed - Examined lightweight agents - Verified probe setup - Checked agent/probe count compared to other systems - Examined credential mappings - Examined external assets - Checked nmap interface on probe - Verified deprecated item list - Created all reports - Assessed reports - Produced Top 15 vulnerabilities docx report - Sent secure email with reports to contact - Sent TimeZest meeting request Is the task resolved? Yes - completed Next step(s) TimeZest meeting request has been sent. Please select a time to meet if you would like to discuss this further.
Had meeting with Pete to discuss this quarter's vulnerability scan results Generated tickets as needed All tasks complete - closing this ticket
pkambouris@wi-engraving.com
pkambouris@wi-engraving.com
2026 Q4 Vulnerability Scan Follow Up
Good evening Pete, Your quarterly vulnerability scan report has been completed and is available in your client folder. Recommended remediation priorities (Top 15): Open Top 15 report Complete report package: Open complete report package The folder contains the following reports: • Pending Remediation EPSS Score Report – classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0–1.0, with 1.0 being most critical). • All Vulnerabilities Report – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity. • Executive Summary Report – a high-level overview of your security posture and network information. • External Scan – detected vulnerabilities and services exposed to the internet. • Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists. Not all vulnerabilities may be feasible to remediate depending on business or technical constraints. Schedule Time With Me Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above. We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems. Sincerely, Chris Knospe
2026 Q4 Remaining remediations
Good evening Pete, Following the quarterly vulnerability review for Wisconsin Engraving Company, Inc., there are no remaining remediations to report. Sincerely, Chris Knospe
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Vulnerability Remediation - Windows 10 (all versions) - Apply Missing OS Updates (Windows 10 EOL - plan upgrade)
Product/System: Windows 10 (all versions)
Affected Systems Count: 7
Finding summary:
Windows 10 (all versions) is missing required updates on the listed hosts.
Apply remaining quality/security updates for the current build via RMM or Windows Update.
Windows 10 is EOL. Do not force a Windows 11 upgrade from this ticket. After those updates, a Windows 11 / new workstation project is a Sales quote and vCIO conversation, then Security suppression of the current OS.
CVE references:
CVE-2025-60724
https://nvd.nist.gov/vuln/detail/CVE-2025-60724
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-60724
Additional CVEs (1473 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5122878. Upgrade to supported Operating System is recommended
- Upgrade to supported Operating System is recommended
- (1 end-of-life component notices omitted) (or the latest available).
Affected Systems:
- ENG22.weco (cad) - 192.168.10.133 [10.0.19045] [1474 vulns]
- DESKTOP-SL7Q6OT.weco (jcarlson) - 192.168.10.119 [10.0.19045] [1474 vulns]
- sales3.weco (nlatz) - 192.168.10.121 [10.0.19045] [1473 vulns]
- eng19.weco (cad) - 192.168.10.122 [10.0.19045] [1473 vulns]
- eng20.weco (dwnuk) - 192.168.10.123 [10.0.19045] [1473 vulns]
- office2.weco (cad) - 192.168.10.109 [10.0.19045] [1473 vulns]
- eng06.weco (emarek) - 192.168.10.111 [10.0.19045] [1473 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
- Windows 10 is EOL: still apply any remaining quality/security updates first; for a Windows 11 / new workstation project, generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current OS
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows Server 2012 (all versions) - End of Support Migration Required
Vulnerability Remediation - Windows Server 2012 (all versions) - End of Support Migration Required
Product/System: Windows Server 2012 (all versions)
Affected Systems Count: 3
Finding summary:
Windows Server 2012 (all versions) needs an infrastructure change on the listed hosts (upgrade, replace, or migrate).
When the fix needs a new server, OS, or workstation: generate a quote (inform the client that you are doing so), then contact vCIO.
Plan upgrade/retire with client approval. Coordinate maintenance windows.
Last browsers these hosts can run: Google Chrome 109.0.5414.129, Microsoft Edge 109.0.1518.140, Mozilla Firefox ESR 115 (latest 115.x). An OS upgrade is required to install a current browser.
CVE references:
CVE-2024-38077
https://nvd.nist.gov/vuln/detail/CVE-2024-38077
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38077
Additional CVEs (1794 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5123066
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- WESHARE - 192.168.10.7 [6.3.9600] [1796 vulns] - OS upgrade required to update browsers
- weacct.weco - 192.168.10.6 [6.3.9600] [1796 vulns] - OS upgrade required to update browsers
- wepdc.weco (rradmin) - 192.168.10.15 [6.3.9600] [1796 vulns] - OS upgrade required to update browsers
Quick-check each host first.
Confirm the OS build/SKU or migration scope matches this finding.
Even for EOL products, check whether a newer final build exists and apply it if the host is behind.
Then stop (escalate to Security as a false positive) if the host is already on a supported platform or is not present.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Complete the infrastructure remediation (default when approved)
- Upgrade, replace, or migrate per Technical guidance and client-approved plan.
- Even when the OS/software is EOL, check whether a newer final build still exists and apply the latest available first.
- When new servers, OS licenses, workstations, or similar are required: generate a quote (inform the client that you are doing so), contact vCIO so they can discuss it with the client, then escalate to Security for suppression of the current asset.
B. Asset not needed - decommission
- Only if the host/service should not exist.
C. Keeping EOL / deferred - notify the client, then escalate to Security for suppression
- After confirming the host is on the latest available build for that EOL product (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Do not request suppression until latest-available was checked and the client was notified.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree project scope, timing, and cutover with the client. If keeping EOL, notify the client before Security suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply the latest available updates for this OS if any exist (EOL releases often have none)
- Create a Sales quote for new hardware or an OS upgrade to a supported release - inform the client that you are doing so
- Contact vCIO so they can discuss the quote with the client
- Escalate to Security for suppression of the current host. Remediation occurs when the old device is retired, or when the purchased software/OS/license update is applied.
- Last browsers this OS can run (a newer browser needs an OS upgrade):
- Google Chrome 109.0.5414.129 - Chrome 110 and later will not install
- Microsoft Edge 109.0.1518.140 - Edge 110 and later will not install
- Mozilla Firefox ESR 115 - install the latest 115.x (115.43.0 as of Oct 13, 2026). Firefox 116 and later will not install
- If a host is already at those versions, stop browser patching. An OS upgrade is required.
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Vulnerability Remediation - Windows 11 (all versions) - Updates Required
Product/System: Windows 11 (all versions)
Affected Systems Count: 1
Finding summary:
Windows 11 (all versions) is missing required updates on the listed hosts.
Apply missing quality/security updates via RMM or Windows Update (or Intune).
Stay on the current Windows version. Coordinate a maintenance window before reboots.
CVE references:
CVE-2026-33824
https://nvd.nist.gov/vuln/detail/CVE-2026-33824
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33824
Additional CVEs (1253 more) are listed in the Client Folder report.
Minimum version to reach:
- Apply Windows Update KB5129242. Upgrade to supported Operating System is recommended
- Apply Windows Update KB5129195
- Upgrade to supported Operating System is recommended (or the latest available).
Affected Systems:
- RECEPTION.weco - 192.168.10.130 [10.0.22631] [1226 vulns]
Quick-check each host first.
Confirm the OS/build on the host matches this finding.
Then stop (escalate to Security as a false positive or no further action) if:
- already at/above the minimum version to reach (build/KB)
- already on the latest quality/security updates for the current Windows version
- the vendor documents this CVE as not applicable or already fixed
Include hostnames, current build, what you verified, and any vendor documentation link.
A fully updated host can still show a CVE until the vendor releases a fix. Do not force a feature upgrade.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply missing OS quality/security updates (default)
- Apply the build/KB listed under Minimum version to reach (or the latest available) via RMM or Windows Update (or Intune).
- Prefer current vendor quality/security updates for the host's existing Windows version.
B. Host not needed - decommission / rebuild
- Only if the host should not exist; do not uninstall the OS.
C. Cannot patch - escalate to Security for suppression
- Examples: OS update channel / RMM broken after troubleshooting, client defers patching after verification, or no approved path yet.
- Do not use suppress only because the host is on an older feature build - feature upgrades need explicit client approval.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree a maintenance window before reboots, feature upgrades, or broad patch pushes. If a user may be interrupted, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Apply missing Windows updates via RMM or Windows Update (or Intune)
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Reboot if Windows Update requires it
- After update, confirm the host has the latest quality/security updates for its current Windows version
- If it is already fully updated and still flagged: escalate to Security as no further action - do not force a feature upgrade
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Apache HTTP Server - Update Required
Vulnerability Remediation - Apache HTTP Server - Update Required
Product/System: Apache HTTP Server
Affected Systems Count: 1
Finding summary:
Apache HTTP Server is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2021-40438
https://nvd.nist.gov/vuln/detail/CVE-2021-40438
Vendor security center:
https://httpd.apache.org/security/vulnerabilities_24.html
Additional CVEs (119 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 2.4.67 (or the latest available).
Affected Systems:
- eng06.weco (emarek) - 192.168.10.111 [120 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - GPL Ghostscript - Update Required
Vulnerability Remediation - GPL Ghostscript - Update Required
Product/System: GPL Ghostscript
Affected Systems Count: 1
Finding summary:
GPL Ghostscript is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2018-19409
https://nvd.nist.gov/vuln/detail/CVE-2018-19409
Additional CVEs (85 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.08.0 (or the latest available).
Affected Systems:
- eng20.weco (dwnuk) - 192.168.10.123 [86 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - fortios - Firmware Update Required
Vulnerability Remediation - fortios - Firmware Update Required
Product/System: fortios
Affected Systems Count: 1
Finding summary:
fortios firmware/software may be outdated on the listed device(s).
Confirm the real vendor, model, and firmware build on the device first.
Check the vendor security advisory for this CVE and model.
If the vendor documents not affected or already fixed: escalate to Security as a false positive with details and the vendor documentation link.
Otherwise apply manufacturer firmware via the vendor tool or device admin.
Coordinate an outage/reboot window.
CVE references:
CVE-2026-24858
https://nvd.nist.gov/vuln/detail/CVE-2026-24858
Vendor security center:
https://fortiguard.fortinet.com/psirt
Additional CVEs (72 more) are listed in the Client Folder report.
Minimum version to reach:
- Kindly update to the latest version recommended by the vendor.
Affected Systems:
- WisconsinEngraving60F - 192.168.10.1 [73 vulns]
Quick-check each device first.
Then stop (escalate to Security as a false positive) if:
- the device is not present
- already at/above the minimum version to reach
- the finding does not match the installed model/firmware
- the vendor documents this CVE as not applicable or already fixed
Include details and the vendor documentation link.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Apply firmware / device software (default when keeping the device)
- Apply manufacturer firmware to the version listed under Minimum version to reach (or the latest available for that model).
- If the product line is EOL, still check for and apply the latest available final firmware for that model before anything else.
B. Device not needed - retire / replace / remove from service
- Only if the device should not remain on the network.
C. EOL / no secure path - notify the client, then escalate to Security for suppression
- After confirming the device is on the latest available firmware for that model (or no further update exists), notify the client of residual risk, record discussion notes to the client, then escalate to Security for suppression.
- Document model, current firmware, and that latest-available was checked.
- Do not request suppression until latest-available was checked and the client was notified.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
Agree an outage window with the client before applying firmware - the device reboots.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- If a support contract has lapsed, do not apply a software or firmware update.
- Notify the client that updates cannot proceed until support is renewed or a replacement is approved
- Create a Sales quote for support renewal, or for replacement/upgrade if the product is also EOL
- Open a vendor case after entitlement is in place (or to confirm support status)
- Do not apply FortiOS firmware if Fortinet support is expired.
- Notify the client, create a Sales quote for Fortinet support renewal (or replacement if the device is also EOL), then open a Fortinet case after entitlement is in place.
- Some FortiOS versions remove SSL-VPN. Confirm SSL-VPN vs IPsec before choosing a target build. If SSL-VPN is still required, stay on a build that still includes it or plan an IPsec cutover first.
- Download firmware from the Fortinet Support Portal (FortiCloud for managed devices). Backup the configuration first. The device reboots.
- Verify the update was successful.
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Tenable Nessus (x64) - Update Required
Vulnerability Remediation - Tenable Nessus (x64) - Update Required
Product/System: Tenable Nessus (x64)
Affected Systems Count: 1
Finding summary:
Tenable Nessus (x64) is a third-party RMM agent on the listed hosts.
Confirm the client uses it and that it is authorized. If it is, update from that vendor's management console - not a silent installer on the host. If the client does not use it or it is not authorized, uninstall it.
CVE references:
CVE-2022-22822
https://nvd.nist.gov/vuln/detail/CVE-2022-22822
Additional CVEs (36 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 10.12.5 (or the latest available).
Affected Systems:
- wepdc.weco (rradmin) - 192.168.10.15 [37 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Client uses it and it is authorized - update from the vendor console (default)
- Confirm the client uses this tool and that it is authorized first.
- Then run the agent upgrade from that vendor's management console to the version listed under Minimum version to reach (or the latest available).
B. Client does not use it / not authorized - uninstall
- Uninstall and remove startup/tasks/services/firewall rules. Document unexpected installs.
C. Authorized but cannot update - escalate to Security for suppression
- You confirmed the client uses it, it is authorized, and it is still behind after the console upgrade path.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm the client uses N-able and that it is authorized
- Check asset inventory, approved software list, and River Run / client deployment records
- If the client does not use it or it is NOT authorized: uninstall and remove startup/tasks/services/firewall rules
- Document unexpected installs as potential unauthorized remote access
- If authorized and the client uses it: update N-able to the reported remediation target
- N-able: run agent upgrade from that vendor's management console (or remove if not your MSP stack)
- Verify version on affected hosts after update
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Microsoft Teams - Application Update Required
Vulnerability Remediation - Microsoft Teams - Application Update Required
Product/System: Microsoft Teams
Affected Systems Count: 6
Finding summary:
Microsoft Teams is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-4863
https://nvd.nist.gov/vuln/detail/CVE-2023-4863
Vendor advisory:
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-4863
Additional CVEs (6 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26260.1701.5139.3736 (or the latest available).
Affected Systems:
- wiseng-dt-25-01.weco (lhenn) - 192.168.10.103 [7 vulns]
- office2.weco (cad) - 192.168.10.109 [7 vulns]
- eng06.weco (emarek) - 192.168.10.111 [7 vulns]
- sales3.weco (nlatz) - 192.168.10.121 [7 vulns]
- DESKTOP-SL7Q6OT.weco (jcarlson) - 192.168.10.119 [2 vulns]
- FrontDesk-PC.weco (customerservice) - 192.168.10.134 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Confirm flagged Teams version - Classic is not always the source
- Classic Teams is sometimes a per-user install
- A user who has not logged into this workstation in a while, or is not the primary user, can still have Classic leftover
- Run the RMM Teams Classic cleanup script for those leftover per-user installs
- Classic/duplicate suspected: R-Security - Teams Classic Cleanup Remediation (Scripts > RR Custom > RR Custom - R-Security Remediation > R-Security - Teams Classic Cleanup Remediation)
- Current Teams behind: automated patching/RMM first
- Live user session only if needed: three-dot menu > Settings > About Teams
- Backstage (CMD/PS): RMM script / installer only - not the Teams UI
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Firebird/InterBase(r) ODBC driver - Update Required
Vulnerability Remediation - Firebird/InterBase(r) ODBC driver - Update Required
Product/System: Firebird/InterBase(r) ODBC driver
Affected Systems Count: 2
Finding summary:
Firebird/InterBase(r) ODBC driver is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2026-40342
https://nvd.nist.gov/vuln/detail/CVE-2026-40342
Additional CVEs (13 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.0.10 (or the latest available). Update to version 5.0.3 (or the latest available)
- (1 end-of-life component notices omitted).
Affected Systems:
- eng06.weco (emarek) - 192.168.10.111 [14 vulns]
- eng20.weco (dwnuk) - 192.168.10.123 [14 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Vulnerability Remediation - WinVerifyTrust Signature Validation Vulnerability - Configuration Change Required
Product/System: WinVerifyTrust Signature Validation Vulnerability
Affected Systems Count: 14
Finding summary:
WinVerifyTrust Signature Validation Vulnerability is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2013-3900
https://nvd.nist.gov/vuln/detail/CVE-2013-3900
Affected Systems:
- DESKTOP-SL7Q6OT.weco (jcarlson) - 192.168.10.119 [1 vulns]
- eng06.weco (emarek) - 192.168.10.111 [1 vulns]
- eng19.weco (cad) - 192.168.10.122 [1 vulns]
- eng20.weco (dwnuk) - 192.168.10.123 [1 vulns]
- ENG22.weco (cad) - 192.168.10.133 [1 vulns]
- office2.weco (cad) - 192.168.10.109 [1 vulns]
- PETES-OFFICE.weco (pkambouris) - 192.168.10.116 [1 vulns]
- sales3.weco (nlatz) - 192.168.10.121 [1 vulns]
- sales4.weco (tstapleton) - 192.168.10.113 [1 vulns]
- SOLIDWORKS.weco (cad) - 192.168.10.129 [1 vulns]
- weacct.weco - 192.168.10.6 [1 vulns]
- wepdc.weco (rradmin) - 192.168.10.15 [1 vulns]
- WESHARE - 192.168.10.7 [1 vulns]
- wiseng-dt-25-01.weco (lhenn) - 192.168.10.103 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture:
schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- WinVerifyTrust / CVE-2013-3900 is Authenticode hardening - not a software install or Windows Update
- Set EnableCertPaddingCheck=1 under HKLM\Software\Microsoft\Cryptography\Wintrust\Config
- On 64-bit hosts also set the Wow6432Node\...\Wintrust\Config copy
- Prefer domain GPO (or Intune) over one-off registry edits
- Verify signed installers and vendor tools still launch after the change
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2013-3900
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - Speculative Store Bypass - Updates Required
Vulnerability Remediation - Speculative Store Bypass - Configuration Change Required
Product/System: Speculative Store Bypass
Affected Systems Count: 13
Finding summary:
Speculative Store Bypass is a configuration / hardening finding.
Correct the listed setting(s) per Technical guidance.
CVE references:
CVE-2018-3639
https://nvd.nist.gov/vuln/detail/CVE-2018-3639
Affected Systems:
- DESKTOP-SL7Q6OT.weco (jcarlson) - 192.168.10.119 [1 vulns]
- eng06.weco (emarek) - 192.168.10.111 [1 vulns]
- eng19.weco (cad) - 192.168.10.122 [1 vulns]
- eng20.weco (dwnuk) - 192.168.10.123 [1 vulns]
- ENG22.weco (cad) - 192.168.10.133 [1 vulns]
- FrontDesk-PC.weco (customerservice) - 192.168.10.134 [1 vulns]
- office2.weco (cad) - 192.168.10.109 [1 vulns]
- PETES-OFFICE.weco (pkambouris) - 192.168.10.116 [1 vulns]
- RECEPTION.weco - 192.168.10.130 [1 vulns]
- sales3.weco (nlatz) - 192.168.10.121 [1 vulns]
- sales4.weco (tstapleton) - 192.168.10.113 [1 vulns]
- SOLIDWORKS.weco (cad) - 192.168.10.129 [1 vulns]
- wiseng-dt-25-01.weco (lhenn) - 192.168.10.103 [1 vulns]
Quick-check each host/domain first.
Then stop (escalate to Security as a false positive) if the configuration is already correct or the finding does not apply.
Include details.
Otherwise choose change, false positive, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Correct the configuration (default)
- Apply the setting change in Technical guidance.
B. Finding does not apply - escalate false positive
- Document what you checked; Security suppresses if appropriate.
C. Client will not change / cannot change - escalate to Security for suppression
- Record client notification/acceptance in discussion notes to the client.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE CHANGING:
If this change may affect access, authentication, mail/DNS, or security posture:
schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must make the change. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Speculative Store Bypass (CVE-2018-3639) is a Windows CPU-mitigation registry setting - not a software install
- Apply latest Windows quality/security updates first - the registry does nothing without those KBs
- Enable the OS mitigation: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
- If FeatureSettingsOverride is missing: set FeatureSettingsOverride=8 and FeatureSettingsOverrideMask=3
- If Override already has a value: add bit 8 (SSB) per Microsoft KB4072698 - do not wipe other Spectre bits already in use
- Prefer domain GPO (or Intune) over one-off registry edits
- Reboot, then verify: Install-Module SpeculationControl; Get-SpeculationControlSettings
- If already patched and mitigations show enabled: escalate to Security as a false positive with hostname, build, and the cmdlet output - then stop
- These mitigations can slow a busy server - discuss with the client if users will notice
- Advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-3639
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - powershellv2 - Update Required
Vulnerability Remediation - powershellv2 - Update Required
Product/System: powershellv2
Affected Systems Count: 12
Finding summary:
powershellv2 is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
Minimum version to reach:
- Disable Windows PowerShell 2.0 on the system (or the latest available).
Affected Systems:
- eng06.weco (emarek) - 192.168.10.111 [1 vulns]
- eng19.weco (cad) - 192.168.10.122 [1 vulns]
- eng20.weco (dwnuk) - 192.168.10.123 [1 vulns]
- ENG22.weco (cad) - 192.168.10.133 [1 vulns]
- FrontDesk-PC.weco (customerservice) - 192.168.10.134 [1 vulns]
- office2.weco (cad) - 192.168.10.109 [1 vulns]
- RECEPTION.weco - 192.168.10.130 [1 vulns]
- sales3.weco (nlatz) - 192.168.10.121 [1 vulns]
- SOLIDWORKS.weco (cad) - 192.168.10.129 [1 vulns]
- weacct.weco - 192.168.10.6 [1 vulns]
- wepdc.weco (rradmin) - 192.168.10.15 [1 vulns]
- WESHARE - 192.168.10.7 [1 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required
Vulnerability Remediation - WinRAR 7.13 (64-bit) - Update Required
Product/System: WinRAR 7.13 (64-bit)
Affected Systems Count: 2
Finding summary:
WinRAR 7.13 (64-bit) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-6218
https://nvd.nist.gov/vuln/detail/CVE-2025-6218
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 7.23 (or the latest available).
Affected Systems:
- SOLIDWORKS.weco (cad) - 192.168.10.129 [2 vulns]
- eng19.weco (cad) - 192.168.10.122 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update WinRAR to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Backstage (CMD/PS): download latest from rarlabs.com; run installer over existing
- Verify version after update; offline agents pending until check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - 7-Zip 26.03 (x64 edition) - Update Required
Vulnerability Remediation - 7-Zip 26.03 (x64 edition) - Update Required
Product/System: 7-Zip 26.03 (x64 edition)
Affected Systems Count: 1
Finding summary:
7-Zip 26.03 (x64 edition) is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2025-0411
https://nvd.nist.gov/vuln/detail/CVE-2025-0411
Additional CVEs (2 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 26.04 (or the latest available).
Affected Systems:
- RECEPTION.weco - 192.168.10.130 [3 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Update 7-Zip to the reported remediation target
- Deploy via automated patching or RMM when patch management is deployed
- Verify version on affected hosts after patch completes
- Backstage (CMD/PS): download latest from 7-zip.org; run installer over existing
- Offline agents: pending until next check-in
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Vulnerability Remediation - FileZilla Client - Update Required
Vulnerability Remediation - FileZilla Client - Update Required
Product/System: FileZilla Client
Affected Systems Count: 1
Finding summary:
FileZilla Client is outdated on the listed hosts.
Update via RMM or a silent installer in Backstage CMD/PS. Use a live user session only if those fail.
CVE references:
CVE-2023-48795
https://nvd.nist.gov/vuln/detail/CVE-2023-48795
Additional CVEs (1 more) are listed in the Client Folder report.
Minimum version to reach:
- Update to version 3.71.1 (or the latest available).
Affected Systems:
- SOLIDWORKS.weco (cad) - 192.168.10.129 [2 vulns]
Quick-check each host first.
Then stop (escalate to Security as a false positive) if the product is not installed or is already at/above the minimum version to reach.
Include hostnames and what you found.
Otherwise choose update, remove, or suppress below and document it in the ticket.
Remediation (pick the most appropriate option):
A. Update (default when still needed)
- Install the updated vendor package (wizard/RMM) to the version listed under Minimum version to reach (or the latest available).
B. Not needed / not in use - uninstall or remove
- Only if the software should not exist on the host.
C. Cannot update or uninstall - escalate to Security for suppression
- You verified it exists at a vulnerable version, and install/update/uninstall is not viable after preferred methods.
- If the product is EOL: check/apply the latest available final build first; if keeping it, notify the client, then escalate to Security.
- Suppression only stops tracking. It does not patch or remove the vulnerability. Residual risk stays until a real fix.
- Client must accept or be notified. Record discussion notes to the client (who, what, hosts, and that risk remains).
Client coordination - READ BEFORE UPDATING:
If this update may interrupt a user, schedule after hours or contact the client first.
If another vendor manages this application, device, workstation, or server: that vendor or the service owner must perform the update. If they are unable or unwilling, escalate to Security for suppression.
===== TECHNICAL GUIDANCE (do this) =====
- Try updates in this order:
1) RMM automated patching or software deployment (preferred)
2) ScreenConnect Backstage CMD/PS or command/script (silent installer)
3) Only if 1 and 2 fail: live remote session with the end user for in-app UI updates
- If this host is a VM, take a pre-update snapshot so you can revert if there are issues.
- Identify product from Product + host list; confirm it is installed on each host before changing anything
- Update/configure to the version listed under Minimum version to reach when present
- If no minimum version is listed: use CVE/product from this ticket + vendor security advisory; document version applied
- Verify the update was successful
- If installer/firmware indicates reboot or service restart: coordinate with client first
===== END TECHNICAL GUIDANCE =====
Source material:
Full scan exports and Top N reports are in the Client Folder under Reports location below.
Reports location (Client Folder): ...\Wisconsin Engraving\Network Documentation\Vulnerability Scans\2026 - Q4
Good evening Pete,
Your quarterly vulnerability scan report has been completed and is available in your client folder.
Recommended remediation priorities (Top 15):
Complete report package:
The folder contains the following reports:
• Pending Remediation EPSS Score Report – classifies vulnerabilities by Exploit Prediction Scoring System (EPSS), which measures the likelihood of exploitation within 30 days (scale 0–1.0, with 1.0 being most critical).
• All Vulnerabilities Report – a comprehensive list of all detected vulnerabilities (internal and external), from critical to low severity.
• Executive Summary Report – a high-level overview of your security posture and network information.
• External Scan – detected vulnerabilities and services exposed to the internet.
• Suppressed Vulnerabilities Report – vulnerabilities that have been suppressed (e.g., false positives or accepted risk) and will not appear on future remediation lists.
Not all vulnerabilities may be feasible to remediate depending on business or technical constraints.
Note: No remediation will begin without your approval. To schedule a discussion, please use the scheduling link above.
We appreciate your commitment to security. Addressing these vulnerabilities is essential for maintaining the protection of your systems.
Sincerely,
Chris Knospe
Check the findings you want as Manage remediation tickets, then click Create selected Manage tickets.
Each selected finding gets its own Manage ticket.
Review's Ticket column pre-checks likely items; you can change the selection here.
Expand a finding to edit the subject or body before you create the ticket.
Use Copy subject / Copy section for manual paste instead.
Where should these tickets go?
Default leaves the ticket for reclassification. Send to security opens it on the Security board as Dispatch. Assign to me puts it on you as Scheduled Internal.