---METADATA---
VENDOR: openshwprojects
PRODUCT: OpenBK7231T_App
AFFECTED_VERSIONS: 0 and later
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A cross-site scripting vulnerability exists in the CHANNEL_SetLabel() function of OpenBK7231T_App, which may allow for unauthorized script execution.

Executive Summary:
A high-severity cross-site scripting vulnerability in OpenBK7231T_App could allow an adjacent attacker to execute arbitrary scripts in the context of the user session.

Vulnerability Details

CVE-ID: CVE-2026-71274

Affected Software: openshwprojects OpenBK7231T_App

Affected Versions: 0 and later

Vulnerability: This is a cross-site scripting (CWE-79) vulnerability located in the CHANNEL_SetLabel() function. The vulnerability is exploitable by an unauthenticated attacker positioned on the adjacent network.

Business Impact

The exploitation of this vulnerability could lead to the compromise of sensitive user information and unauthorized actions performed on behalf of legitimate users. With a CVSS score of 8.5, this high-severity flaw represents a significant risk to the integrity and confidentiality of the application environment.

Remediation Plan

Immediate Action: Monitor the official repository for the release of a security patch and apply it immediately upon availability.

Proactive Monitoring: Review web application logs for unusual request patterns, specifically focusing on parameters interacting with channel labels.

Compensating Controls: Implement a Web Application Firewall to filter malicious scripts and restrict access to the management interface from untrusted networks.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw requires the attacker to be on the adjacent network, which limits the potential attack surface.

Analyst Recommendation

Given the high CVSS score, organizations should prioritize the mitigation of this vulnerability. As no patch is currently identified, administrators must rely on network segmentation and strict access controls to prevent unauthorized access to the application interface until an official vendor update is provided.

---METADATA---
VENDOR: usememos
PRODUCT: memos
AFFECTED_VERSIONS: 0 through 0.29.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A race condition vulnerability exists in the Memos webhook dispatch function within the safeDialContext implementation.

Executive Summary:
Memos is susceptible to a race condition in its webhook dispatch function, which could be leveraged by an authenticated user to achieve unintended network interactions.

Vulnerability Details

CVE-ID: CVE-2026-71272

Affected Software: usememos memos

Affected Versions: 0 through 0.29.1

Vulnerability: This vulnerability is categorized as a Time-of-Check to Time-of-Use (TOCTOU) race condition (CWE-367) located in the safeDialContext function. An authenticated attacker can manipulate the dispatch process to potentially bypass intended security checks during the connection phase.

Business Impact

The CVSS score of 8.5 highlights the severity of this flaw. By exploiting this race condition, an attacker may be able to reach internal resources that should be restricted, potentially leading to unauthorized information disclosure or interaction with internal API endpoints.

Remediation Plan

Immediate Action: Monitor the official Memos repository and apply the security update as soon as the vendor releases a patched version addressing the race condition.

Proactive Monitoring: Review application logs for unexpected or rapid webhook dispatch attempts that could indicate an exploitation effort.

Compensating Controls: Employ network-level micro-segmentation to ensure the Memos application has limited visibility into the local network environment.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. Race conditions are inherently difficult to exploit reliably, but they remain a high-risk vector in network-facing components.

Analyst Recommendation

Due to the nature of race conditions, patching is the only definitive way to eliminate the vulnerability. Administrators should ensure that the Memos application is isolated within the network until a permanent fix is applied and verified.

---METADATA---
VENDOR: usememos
PRODUCT: memos
AFFECTED_VERSIONS: 0 through 0.29.1
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A server-side request forgery vulnerability exists in the Memos webhook URL validation logic, specifically within the isReservedIP function.

Executive Summary:
The Memos application contains a server-side request forgery vulnerability in its webhook validation logic that could allow an authenticated user to bypass security controls.

Vulnerability Details

CVE-ID: CVE-2026-71271

Affected Software: usememos memos

Affected Versions: 0 through 0.29.1

Vulnerability: The flaw, classified as CWE-918, exists in the isReservedIP function within the webhook validation module. An authenticated attacker can exploit this to bypass IP restrictions and force the application to interact with unintended network targets.

Business Impact

With a CVSS score of 8.5, this vulnerability represents a significant risk. If exploited, an attacker could potentially interact with internal infrastructure, leading to unauthorized data access or the bypassing of perimeter security controls for internal-only services.

Remediation Plan

Immediate Action: Users should monitor the official Memos repository for a patched release and update immediately upon availability.

Proactive Monitoring: Audit webhook configuration logs for entries pointing to internal IP addresses or unusual network destinations.

Compensating Controls: Implement strict network-level egress filtering for the server hosting Memos to ensure it cannot communicate with internal-only network segments.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherent to the logic handling webhook validations, which requires authenticated access to trigger.

Analyst Recommendation

The reliance on webhook validation makes this a critical security concern for deployments that allow external integrations. Organizations should restrict administrative access and apply the forthcoming patch as soon as the vendor provides a remediation update.

---METADATA---
VENDOR: Stirling-Tools
PRODUCT: Stirling-PDF
AFFECTED_VERSIONS: All versions
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A server-side request forgery vulnerability exists in the Stirling-PDF ConvertWebsiteToPDF endpoint, allowing unauthenticated attackers to potentially access internal resources.

Executive Summary:
An unauthenticated server-side request forgery vulnerability in Stirling-PDF allows attackers to make unauthorized requests to internal network resources.

Vulnerability Details

CVE-ID: CVE-2026-71270

Affected Software: Stirling-Tools Stirling-PDF

Affected Versions: All versions

Vulnerability: This is a Server-Side Request Forgery (CWE-918) vulnerability in the POST /api/v1/convert/url/pdf endpoint. The vulnerability is exploitable by unauthenticated attackers, as indicated by the CVSS vector.

Business Impact

With a CVSS score of 8.6, this vulnerability represents a significant threat to internal network security. An attacker could leverage this flaw to probe internal infrastructure, access sensitive metadata services, or interact with non-public internal web applications, bypassing perimeter defenses.

Remediation Plan

Immediate Action: Check the Stirling-PDF repository for security updates and apply the latest version to mitigate the SSRF flaw.

Proactive Monitoring: Monitor network traffic for unexpected outbound requests originating from the server hosting Stirling-PDF, particularly requests directed toward internal IP ranges.

Compensating Controls: Restrict the application server's ability to initiate outbound network connections to internal resources using firewall rules or network segmentation.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to its unauthenticated nature and potential to bypass network perimeters.

Analyst Recommendation

This vulnerability is highly critical due to its potential for internal network reconnaissance. Users should restrict access to the Stirling-PDF instance until a patch is applied and verify that the application cannot reach sensitive internal endpoints.

---METADATA---
VENDOR: thiagoralves
PRODUCT: OpenPLC_v3
AFFECTED_VERSIONS: 0 and later
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
OpenPLC Runtime v3 contains a path traversal vulnerability in its compile_program function, allowing remote authenticated users to write arbitrary files to the filesystem.

Executive Summary:
A critical path traversal vulnerability in OpenPLC Runtime v3 allows authenticated attackers to achieve remote code execution by overwriting arbitrary system files.

Vulnerability Details

CVE-ID: CVE-2026-71268

Affected Software: thiagoralves OpenPLC_v3

Affected Versions: 0 and later

Vulnerability: The application fails to validate the file path during the processing of uploaded Structured Text files, enabling a path traversal flaw (CWE-22) that permits arbitrary file writes. The vulnerability is accessible to authenticated users, though the presence of hardcoded default credentials significantly lowers the barrier to entry.

Business Impact

Successful exploitation grants an attacker the ability to overwrite sensitive system configuration files or inject malicious code into startup scripts. Given the CVSS score of 9.9, this vulnerability poses a catastrophic risk to system integrity and availability, potentially leading to a complete compromise of the underlying host and any connected industrial control systems.

Remediation Plan

Immediate Action: Upgrade to the latest version of OpenPLC v3 immediately to incorporate path validation logic into the compile_program function.

Proactive Monitoring: Review access logs for unusual file upload activity or attempts to access system directories such as /etc/ or /home/.

Compensating Controls: Change the default credentials (openplc:openplc) immediately and restrict network access to the OpenPLC web interface to trusted management subnets.

Exploitation Status

Public Exploit Available: No (exploit_available: unknown)

Analyst Notes: As of Aug 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly exploitable due to the combination of insecure file handling and weak default authentication.

Analyst Recommendation

This is a critical vulnerability that requires immediate remediation. Administrators must prioritize updating the software and enforcing strong, unique credentials to prevent unauthorized access and potential remote code execution.

---METADATA---
VENDOR: rxi
PRODUCT: microtar
AFFECTED_VERSIONS: 0 and later
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A stack buffer overflow exists in rxi microtar due to improper boundary checks when copying filenames into the header structure.

Executive Summary:
A critical stack buffer overflow in the rxi microtar library allows for potential remote code execution when processing maliciously crafted filenames.

Vulnerability Details

CVE-ID: CVE-2026-71267

Affected Software: rxi microtar

Affected Versions: 0 and later

Vulnerability: The functions mtar_write_file_header and mtar_write_dir_header perform a strcpy operation into a fixed-size 100-byte stack buffer without verifying the input length. This allows an attacker to supply a filename exceeding 99 characters, triggering an overflow that can be exploited by unauthenticated remote attackers.

Business Impact

Successful exploitation of this buffer overflow could lead to arbitrary code execution, allowing an attacker to gain control over the host process. Given the 9.8 CVSS score, this represents a major threat to system integrity and availability, particularly for applications that handle untrusted archives or user-provided filenames.

Remediation Plan

Immediate Action: Review applications utilizing the microtar library to ensure all input filenames are strictly validated for length before being passed to library functions.

Proactive Monitoring: Monitor for application crashes or segmentation faults that may indicate an attempt to exploit memory corruption vulnerabilities.

Compensating Controls: Compile the application with modern memory safety protections, such as stack canaries and Address Space Layout Randomization (ASLR), to increase the difficulty of successful exploitation.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Aug 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is inherent to the library's design and requires developers to implement input validation at the call site.

Analyst Recommendation

Developers should immediately audit their use of the microtar library and implement mandatory length checks for all filenames. Until a formal library update is available, manual input sanitization is the most effective way to mitigate this critical risk.

---METADATA---
VENDOR: Aircoookie
PRODUCT: WLED
AFFECTED_VERSIONS: 0 and later
CONFIDENCE: medium
MISSING: patch
---END_METADATA---

Description Summary:
The WLED project contains a broken access control vulnerability in the GET /json/cfg endpoint that allows unauthenticated modification of configuration settings.

Executive Summary:
An unauthenticated broken access control flaw in the WLED configuration endpoint exposes the device to unauthorized settings modification.

Vulnerability Details

CVE-ID: CVE-2026-71264

Affected Software: Aircoookie WLED

Affected Versions: 0 and later

Vulnerability: This vulnerability (CWE-862) exists within the /json/cfg endpoint. It permits an unauthenticated attacker to perform unauthorized configuration changes, which could lead to full control over the device settings.

Business Impact

The CVSS score of 8.2 highlights a high risk of unauthorized configuration manipulation. In an industrial or commercial lighting environment, this could lead to service disruption, device bricking, or the use of compromised devices as a pivot point within the internal network.

Remediation Plan

Immediate Action: Review the official WLED project repository for security guidance and apply any available firmware updates. If no update is available, restrict access to the WLED interface to trusted network segments only.

Proactive Monitoring: Monitor network traffic to the WLED device for unauthorized access to the /json/cfg endpoint.

Compensating Controls: Place the device on an isolated VLAN with no direct access from the public internet or untrusted internal segments.

Exploitation Status

Public Exploit Available: No confirmed public exploit is available in the provided data.

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The accessibility of the configuration endpoint without authentication makes this a significant risk for exposed IoT devices.

Analyst Recommendation

Users of WLED should prioritize network-level isolation for these devices until a formal patch is applied. The lack of authentication on the configuration endpoint is a severe security oversight that must be mitigated by restricting network exposure as a primary defense.

---METADATA---
VENDOR: IoTSharp
PRODUCT: IoTSharp
AFFECTED_VERSIONS: All versions prior to the patched version
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
IoTSharp fails to enforce authorization on its BlobStorageController, allowing unauthenticated remote attackers to perform arbitrary file operations via path traversal.

Executive Summary:
A critical authentication bypass and path traversal vulnerability in IoTSharp is currently being actively exploited in the wild.

Vulnerability Details

CVE-ID: CVE-2026-71262

Affected Software: IoTSharp IoTSharp

Affected Versions: All versions prior to the patched version

Vulnerability: The application fails to apply authorization requirements to the BlobStorageController, permitting unauthenticated attackers to access sensitive endpoints. Furthermore, improper input sanitization on file paths allows for arbitrary file system access, including the potential for remote code execution via web shell upload.

Business Impact

This vulnerability carries a CVSS score of 9.8, reflecting its critical severity. Successful exploitation allows unauthorized actors to read, modify, or delete sensitive data, and potentially gain full control over the host system. Given its inclusion in the CISA Known Exploited Vulnerabilities (KEV) catalog, the urgency for remediation is extreme to prevent data breaches or total system compromise.

Remediation Plan

Immediate Action: Update to the latest version of IoTSharp as soon as it is made available by the vendor to implement mandatory authorization checks and path sanitization.

Proactive Monitoring: Review application and web server access logs for requests targeting the BlobStorageController or unusual file path patterns that suggest directory traversal attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to block directory traversal sequences (such as double dots and slashes) and restrict access to the BlobStorageController endpoints.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: This vulnerability is confirmed to be actively exploited in the wild as of August 4, 2026. The combination of missing authentication and path traversal makes this an highly attractive target for threat actors.

Analyst Recommendation

Due to confirmed active exploitation in the wild, organizations must prioritize this vulnerability immediately. Apply the latest available vendor security updates and monitor network traffic for signs of compromise until patching is complete.

---METADATA---
VENDOR: ESPHome
PRODUCT: esphome
AFFECTED_VERSIONS: 0 through 2026.7.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
ESPHome through 2026.7.0 contains a vulnerability related to incomplete validation of data, which may allow for significant system impact.

Executive Summary:
ESPHome versions up to 2026.7.0 are affected by an input validation vulnerability that could result in total system compromise.

Vulnerability Details

CVE-ID: CVE-2026-71259

Affected Software: ESPHome esphome

Affected Versions: 0 through 2026.7.0

Vulnerability: This vulnerability involves a flaw in configuration validation (CWE-184). The attack vector is local, requiring user interaction to trigger, but could lead to high confidentiality, integrity, and availability impacts.

Business Impact

With a CVSS score of 8.6, this vulnerability represents a high risk to organizational security. Successful exploitation could lead to unauthorized control over the affected ESPHome environment, potentially allowing attackers to manipulate device configurations or gain unauthorized access to the underlying system.

Remediation Plan

Immediate Action: Monitor the official ESPHome GitHub repository for the release of a security patch and apply it as soon as it becomes available.

Proactive Monitoring: Review system configuration logs for unexpected validation errors or unauthorized modifications to device settings.

Compensating Controls: Ensure devices running ESPHome are isolated within restricted network segments to limit the potential impact of a local exploit.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability.

Analyst Recommendation

Given the high CVSS score and the potential for total impact, administrators should prioritize this issue. Closely track vendor communications regarding the patch, and ensure that all affected instances are updated once a fix is released.

---METADATA---
VENDOR: debevv
PRODUCT: nanoMODBUS
AFFECTED_VERSIONS: 0 through 1.23.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
nanoMODBUS contains an out-of-bounds stack read and wild-pointer write vulnerability in its Modbus identification response handling, which can be triggered by a malicious server.

Executive Summary:
A critical memory corruption vulnerability in the nanoMODBUS library allows for potential arbitrary code execution via a malicious server response.

Vulnerability Details

CVE-ID: CVE-2026-71256

Affected Software: debevv nanoMODBUS

Affected Versions: 0 through 1.23.0

Vulnerability: The library fails to perform bounds checking on the object_id field when processing Modbus Device Identification responses (CWE-125). An unauthenticated remote attacker can provide a crafted response that causes an out-of-bounds read, leading to an arbitrary-address write with controlled data.

Business Impact

The ability to perform arbitrary-address writes typically results in remote code execution or complete application crashes. With a CVSS score of 9.8, this vulnerability poses a severe threat to the availability and integrity of any system integrating the nanoMODBUS library.

Remediation Plan

Immediate Action: Monitor the official debevv nanoMODBUS GitHub repository for the release of a patched version. If a patch is not yet available, evaluate the feasibility of disabling Modbus identification features in affected deployments.

Proactive Monitoring: Monitor network traffic for anomalous Modbus protocol traffic patterns or unexpected device identification responses.

Compensating Controls: Deploy network-based intrusion detection systems to inspect Modbus traffic and filter out malformed or suspicious identification response packets.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The technical nature of the flaw makes it highly exploitable for memory corruption attacks.

Analyst Recommendation

This vulnerability is critical due to the potential for memory corruption and code execution. Organizations should track the project repository for updates and move to version 1.23.1 or later as soon as it becomes available.

---METADATA---
VENDOR: debevv
PRODUCT: nanoMODBUS
AFFECTED_VERSIONS: 0 through 1.23.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A buffer overflow vulnerability exists in nanoMODBUS versions up to 1.23.0, potentially allowing for arbitrary code execution or denial of service.

Executive Summary:
The nanoMODBUS library contains a buffer overflow vulnerability that poses a high risk of service disruption or unauthorized data access.

Vulnerability Details

CVE-ID: CVE-2026-71255

Affected Software: debevv nanoMODBUS

Affected Versions: 0 through 1.23.0

Vulnerability: This is a buffer overflow vulnerability (CWE-787) that occurs due to improper bounds checking. It is remotely exploitable and does not require authentication or user interaction.

Business Impact

The CVSS score of 8.6 reflects the significant risk posed by this vulnerability. Exploitation can lead to service crashes or the compromise of data integrity, which may disrupt critical industrial or automation processes reliant on the nanoMODBUS library.

Remediation Plan

Immediate Action: Check for available vendor updates and apply the latest version of nanoMODBUS immediately upon release.

Proactive Monitoring: Monitor network traffic for malformed MODBUS packets or unexpected spikes in CPU usage that may indicate a crash or exploitation attempt.

Compensating Controls: Deploy network-level intrusion detection systems to identify and block traffic patterns indicative of buffer overflow attempts against MODBUS services.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability.

Analyst Recommendation

The severity of this flaw necessitates immediate attention. Organizations utilizing nanoMODBUS should evaluate their exposure and prepare for an urgent update once the vendor provides a patched release.

---METADATA---
VENDOR: debevv
PRODUCT: nanoMODBUS
AFFECTED_VERSIONS: nanoMODBUS through v1.23.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
An out-of-bounds write vulnerability in nanoMODBUS allows unauthenticated attackers to corrupt memory and potentially achieve remote code execution via a malformed Modbus request.

Executive Summary:
A critical out-of-bounds write vulnerability in nanoMODBUS is confirmed to be under active exploitation in the wild.

Vulnerability Details

CVE-ID: CVE-2026-71254

Affected Software: debevv nanoMODBUS

Affected Versions: nanoMODBUS through v1.23.0

Vulnerability: The Modbus server-side function handle_read_file_record fails to validate the cumulative response size of sub-requests, leading to an integer overflow in the accumulator. This allows unauthenticated network clients to trigger an out-of-bounds write, corrupting memory beyond the designated buffer.

Business Impact

With a CVSS score of 9.8, this flaw poses a severe risk to operational technology and embedded systems. Exploitation can lead to a complete denial of service or remote code execution, which may result in the loss of control over industrial processes or critical infrastructure. Inclusion in the CISA KEV catalog necessitates immediate administrative attention.

Remediation Plan

Immediate Action: Update to the latest version of nanoMODBUS to ensure proper bounds checking on cumulative response sizes is enforced.

Proactive Monitoring: Monitor network traffic for malformed Modbus packets or unexpected server crashes which may indicate exploitation attempts.

Compensating Controls: Implement strict network segmentation and firewall rules to limit access to Modbus services to authorized, trusted IP addresses only.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: This vulnerability is confirmed to be actively exploited in the wild as of August 5, 2026. The lack of memory protection on many embedded targets makes this vulnerability particularly dangerous.

Analyst Recommendation

Given the active exploitation and the critical nature of the flaw, IT and OT teams should treat this as a top-priority item. Ensure all deployments of nanoMODBUS are updated and verify that network-level access controls are strictly enforced.

---METADATA---
VENDOR: raghav993
PRODUCT: toner-management
AFFECTED_VERSIONS: All versions
CONFIDENCE: medium
MISSING: patch
---END_METADATA---

Description Summary:
The toner-management application contains missing authorization checks in its administrative state-changing handlers, allowing unauthorized users to modify system states.

Executive Summary:
A missing authorization vulnerability in the toner-management application allows unauthenticated attackers to perform administrative state changes, creating a critical risk to system integrity.

Vulnerability Details

CVE-ID: CVE-2026-71252

Affected Software: raghav993 toner-management

Affected Versions: All versions

Vulnerability: This vulnerability (CWE-862) involves the absence of necessary authorization checks for administrative functions. An unauthenticated attacker can interact with state-changing handlers, potentially leading to unauthorized system modifications.

Business Impact

With a CVSS score of 8.2, this vulnerability represents a significant threat to the operational integrity of the toner-management system. An attacker could alter configurations or system states without authentication, potentially leading to unauthorized control, service disruption, or data manipulation that could impact business operations.

Remediation Plan

Immediate Action: Review the project repository for available security patches or configuration changes, and restrict network access to the administrative interfaces of the application.

Proactive Monitoring: Monitor server access logs for requests directed at administrative endpoints originating from unauthorized or external IP addresses.

Compensating Controls: Deploy a Web Application Firewall (WAF) to block unauthorized access attempts to administrative URLs and state-changing API endpoints.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly accessible as it does not require authentication to trigger.

Analyst Recommendation

Due to the lack of authentication requirements for critical administrative functions, this vulnerability should be addressed with high urgency. If an official patch is not yet available, organizations should move the application to a restricted network segment inaccessible to untrusted users.

---METADATA---
VENDOR: Totolink
PRODUCT: A8000RU
AFFECTED_VERSIONS: 7.1cu.643_b20200521
---END_METADATA---

Description Summary:
An unauthenticated remote OS command injection vulnerability exists in the Totolink A8000RU CGI handler via the merge parameter in the setWiFiEasyCfg function.

Executive Summary:
A critical OS command injection vulnerability in the Totolink A8000RU router allows unauthenticated remote attackers to execute arbitrary commands.

Vulnerability Details

CVE-ID: CVE-2026-7125

Affected Software: Totolink A8000RU

Affected Versions: 7.1cu.643_b20200521

Vulnerability: This vulnerability occurs in the setWiFiEasyCfg function within /cgi-bin/cstecgi.cgi. The merge parameter is inadequately sanitized, allowing remote command injection by an unauthenticated attacker.

Business Impact

The device is subject to total compromise, which poses a significant threat to internal network security. The 9.8 CVSS score justifies treating this as a high-priority security issue.

Remediation Plan

Immediate Action: Update to the latest firmware version and disable the Wi-Fi Easy Configuration feature if possible.

Proactive Monitoring: Review router logs for any suspicious system-level commands being executed.

Compensating Controls: Restrict management interface access to local or trusted administrative subnets only.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of April 27, 2026, a public exploit is available, making this a high-risk vulnerability.

Analyst Recommendation

All affected users should immediately update their firmware. If a patch is unavailable, the device must be isolated from the WAN to prevent remote exploitation.

---METADATA---
VENDOR: Adaltas
PRODUCT: backmeup
AFFECTED_VERSIONS: 0 through 0.0.2
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The backmeup npm package is vulnerable to OS command injection due to insecure concatenation of input parameters when constructing shell commands.

Executive Summary:
A high severity OS command injection vulnerability in the Adaltas backmeup package allows authenticated users to execute arbitrary commands on the underlying host system.

Vulnerability Details

CVE-ID: CVE-2026-71243

Affected Software: Adaltas backmeup

Affected Versions: 0 through 0.0.2

Vulnerability: This vulnerability involves CWE-78: OS Command Injection. The software fails to sanitize input options such as name, source, destination, and filter before including them in shell command strings, allowing an authenticated user with low privileges to inject and execute arbitrary system commands.

Business Impact

The vulnerability carries a CVSS score of 8.8, reflecting the high risk posed by successful exploitation. An attacker successfully leveraging this flaw could gain full control over the host system, leading to unauthorized data exfiltration, modification of critical system files, or complete service disruption.

Remediation Plan

Immediate Action: Currently, there is no vendor-supplied patch available. Users should evaluate the necessity of the backmeup package and consider removing or disabling it until a secure version is released.

Proactive Monitoring: Security teams should monitor system logs for suspicious process execution patterns or unexpected shell commands originating from the service user account.

Compensating Controls: Implement strict input validation or use a Web Application Firewall (WAF) to inspect and block malicious payloads containing shell metacharacters in request parameters.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the direct concatenation of user-controlled input into system-level commands.

Analyst Recommendation

Given the high CVSS score and the nature of command injection, this vulnerability poses a severe threat to system integrity. Organizations using the backmeup package are advised to restrict access to the application and monitor for signs of unauthorized activity while awaiting an official security update.

---METADATA---
VENDOR: crater-invoice
PRODUCT: crater
AFFECTED_VERSIONS: 6.0.6
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Crater fails to verify company ownership when accessing notes, allowing authenticated users to bypass authorization checks and view or manage notes belonging to other companies.

Executive Summary:
An authorization bypass vulnerability in Crater version 6.0.6 allows authenticated users to access unauthorized data, posing a significant risk to data confidentiality and integrity.

Vulnerability Details

CVE-ID: CVE-2026-71242

Affected Software: crater-invoice crater

Affected Versions: 6.0.6

Vulnerability: This is an authorization bypass vulnerability (CWE-639) where the application relies on blanket permission checks rather than validating that the requesting user owns the specific data record. The flaw is accessible to authenticated users with low privileges.

Business Impact

Successful exploitation permits unauthorized access to sensitive financial notes and records across different company accounts. With a CVSS score of 8.2, this high-severity flaw could lead to significant data breaches, regulatory non-compliance, and loss of client trust by allowing lateral movement between isolated business entities within the platform.

Remediation Plan

Immediate Action: Update the Crater installation to the latest patched version provided by the vendor.

Proactive Monitoring: Review system access logs for unusual patterns, specifically looking for users accessing note records outside of their assigned company context.

Compensating Controls: Implement strict database-level row security or application-layer middleware to enforce company-ownership checks until the official patch is deployed.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable by any authenticated user due to the missing ownership comparison logic.

Analyst Recommendation

Given the high CVSS score and the direct impact on data isolation, organizations should prioritize patching this vulnerability. Administrators must verify that their environment is updated to a version beyond 6.0.6 to ensure that company-ownership validation is correctly enforced.

---METADATA---
VENDOR: Totolink
PRODUCT: A8000RU
AFFECTED_VERSIONS: 7.1cu.643_b20200521
---END_METADATA---

Description Summary:
An unauthenticated remote OS command injection vulnerability exists in the Totolink A8000RU CGI handler via the addrPrefixLen parameter in the setIpv6LanCfg function.

Executive Summary:
A critical OS command injection vulnerability in the Totolink A8000RU router allows unauthenticated remote attackers to execute arbitrary commands.

Vulnerability Details

CVE-ID: CVE-2026-7124

Affected Software: Totolink A8000RU

Affected Versions: 7.1cu.643_b20200521

Vulnerability: The vulnerability is located in the setIpv6LanCfg function of the /cgi-bin/cstecgi.cgi file. An unauthenticated attacker can supply a malicious addrPrefixLen parameter to trigger OS command injection.

Business Impact

This flaw permits total device takeover, which can lead to severe security breaches, including data exfiltration and denial of service. The 9.8 CVSS score reflects the high impact on confidentiality, integrity, and availability.

Remediation Plan

Immediate Action: Apply the vendor-supplied firmware update and disable IPv6 if it is not currently in use.

Proactive Monitoring: Monitor router logs for anomalous execution attempts or unexpected configuration changes.

Compensating Controls: Use a firewall to block access to the management interface from the WAN side.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of April 27, 2026, a public exploit is available for this vulnerability.

Analyst Recommendation

Immediate remediation is essential. Users should prioritize updating their firmware to the latest version to mitigate this critical risk.

---METADATA---
VENDOR: absmach
PRODUCT: magistrala
AFFECTED_VERSIONS: 0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Magistrala Rules Engine allows authenticated users to execute arbitrary Go or Lua scripts server-side, leading to code injection.

Executive Summary:
A critical code injection vulnerability in the Magistrala Rules Engine allows authenticated attackers to execute arbitrary scripts on the server.

Vulnerability Details

CVE-ID: CVE-2026-71235

Affected Software: absmach magistrala

Affected Versions: 0

Vulnerability: This vulnerability (CWE-94) occurs because the Rules Engine allows authenticated users to embed and execute Go or Lua scripts server-side, which can be leveraged to gain unauthorized system control.

Business Impact

An attacker successfully exploiting this vulnerability gains the ability to execute arbitrary code with the privileges of the Magistrala service, potentially resulting in full system compromise. The CVSS score of 8.8 reflects the high impact on system integrity and the potential for lateral movement within an IoT infrastructure.

Remediation Plan

Immediate Action: Review vendor advisories for available security patches or configuration changes that restrict script execution capabilities within the Rules Engine.

Proactive Monitoring: Audit all user-created rules and monitor server processes for anomalous script execution or unauthorized outbound network traffic originating from the engine.

Compensating Controls: Restrict access to the Rules Engine creation interface to only highly trusted administrators and isolate the Magistrala instance within a segmented network zone.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The requirement for authenticated access necessitates robust identity management to prevent exploitation.

Analyst Recommendation

This vulnerability is highly dangerous due to the nature of server-side code execution. Organizations should immediately review their usage of the Magistrala Rules Engine and apply updates as soon as the vendor provides a formal patch.

---METADATA---
VENDOR: InvoiceNinja
PRODUCT: InvoiceNinja
AFFECTED_VERSIONS: 5.0.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
InvoiceNinja v5.0.0 is susceptible to Stored Cross-site Scripting (XSS) due to the unsafe rendering of the terms field in the client portal via the Laravel Blade raw output directive.

Executive Summary:
InvoiceNinja v5.0.0 contains a Cross-site Scripting vulnerability that allows authenticated users to execute arbitrary scripts in the client portal, posing a significant risk to user session security.

Vulnerability Details

CVE-ID: CVE-2026-71233

Affected Software: InvoiceNinja InvoiceNinja

Affected Versions: 5.0.0

Vulnerability: The application uses the Laravel Blade {!! !!} directive to render the terms field, which fails to sanitize input, allowing an authenticated user with sufficient privileges to inject malicious scripts that execute in the context of other users.

Business Impact

With a CVSS score of 8.7, this XSS flaw facilitates session hijacking, unauthorized account actions, and potential data theft from the client portal. Such compromises can lead to severe reputational damage and the loss of sensitive financial or client data.

Remediation Plan

Immediate Action: Review vendor documentation for the latest stable release and apply all available security updates to address the improper rendering of user input.

Proactive Monitoring: Inspect web application logs for suspicious script injection patterns in invoice or quote templates and monitor for unauthorized portal access attempts.

Compensating Controls: Utilize a Web Application Firewall (WAF) with robust XSS filtering rules to detect and block malicious payloads submitted via the invoice terms field.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 6, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability requires authenticated access, which limits the attack surface to existing users or compromised accounts.

Analyst Recommendation

Security teams should treat this XSS vulnerability as a priority, particularly for public-facing portals. Immediate remediation through software updates is essential to prevent session-based attacks that could lead to unauthorized data access or platform manipulation.

---METADATA---
VENDOR: thebradleysanders
PRODUCT: IOTSmartHome
AFFECTED_VERSIONS: 0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The IOTSmartHome platform is vulnerable to SQL injection via the lastLogin cookie, allowing unauthenticated attackers to bypass authentication and extract sensitive database information.

Executive Summary:
A critical SQL injection vulnerability in IOTSmartHome allows unauthenticated attackers to bypass authentication and exfiltrate sensitive data from the underlying database.

Vulnerability Details

CVE-ID: CVE-2026-71231

Affected Software: thebradleysanders IOTSmartHome

Affected Versions: 0

Vulnerability: This is an SQL Injection (CWE-89) vulnerability located in the checkCookie function within gui/login.php. The application fails to sanitize the decoded contents of the lastLogin cookie before concatenating it into a database query, enabling attackers to inject malicious SQL commands.

Business Impact

Successful exploitation allows an attacker to bypass authentication mechanisms, granting them unauthorized access to the application. Furthermore, the use of UNION-based injection allows for the extraction of sensitive information, including user credentials, which could lead to widespread account compromise and a severe breach of confidentiality.

Remediation Plan

Immediate Action: Update IOTSmartHome to the latest version immediately to receive the necessary input sanitization fixes. If an update is unavailable, disable the affected login functionality or restrict access to the web interface.

Proactive Monitoring: Monitor database logs for suspicious query patterns, such as unexpected UNION statements or syntax errors indicative of injection attempts. Review authentication logs for unusual login activity.

Compensating Controls: Utilize a WAF to inspect and block incoming HTTP requests containing suspicious base64-encoded payloads in the lastLogin cookie.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of August 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly exploitable due to the predictable nature of the cookie-based authentication flow.

Analyst Recommendation

Given the critical severity and the ease of exploitation, immediate remediation is required. Ensure that all database interactions are parameterized and that input validation is strictly enforced to prevent further injection risks.

---METADATA---
VENDOR: Totolink
PRODUCT: A8000RU
AFFECTED_VERSIONS: 7.1cu.643_b20200521
---END_METADATA---

Description Summary:
An unauthenticated remote OS command injection vulnerability in the Totolink A8000RU CGI handler occurs via the setIptvCfg function.

Executive Summary:
A critical OS command injection vulnerability in the Totolink A8000RU router allows unauthenticated remote attackers to execute arbitrary commands.

Vulnerability Details

CVE-ID: CVE-2026-7123

Affected Software: Totolink A8000RU

Affected Versions: 7.1cu.643_b20200521

Vulnerability: This vulnerability affects the setIptvCfg function in the /cgi-bin/cstecgi.cgi file, where improper handling of the setIptvCfg argument allows for remote OS command injection.

Business Impact

This vulnerability allows an attacker to gain full control of the network device. The CVSS score of 9.8 indicates that this is a critical risk, potentially allowing an attacker to reroute traffic or disable security controls.

Remediation Plan

Immediate Action: Update to the latest firmware version and disable the IPTV configuration feature if not strictly required.

Proactive Monitoring: Monitor for unusual traffic patterns and unauthorized configuration changes on the router.

Compensating Controls: Implement strict network access control lists (ACLs) to prevent unauthorized access to the router's management interface.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of April 27, 2026, a public exploit is available, making this vulnerability highly accessible to malicious actors.

Analyst Recommendation

The severity and exploitability of this vulnerability demand immediate attention. Users should update their firmware to the latest available version and apply recommended network hardening techniques immediately.

---METADATA---
VENDOR: Totolink
PRODUCT: A8000RU
AFFECTED_VERSIONS: 7.1cu.643_b20200521
---END_METADATA---

Description Summary:
An unauthenticated remote OS command injection vulnerability exists in the Totolink A8000RU CGI handler via the enable parameter in the setUPnPCfg function.

Executive Summary:
A critical OS command injection vulnerability in the Totolink A8000RU router allows unauthenticated remote attackers to execute arbitrary commands.

Vulnerability Details

CVE-ID: CVE-2026-7122

Affected Software: Totolink A8000RU

Affected Versions: 7.1cu.643_b20200521

Vulnerability: The vulnerability resides in the setUPnPCfg function within the /cgi-bin/cstecgi.cgi file. Lack of input sanitization on the enable argument permits remote OS command injection by an unauthenticated user.

Business Impact

The flaw provides an attacker with the ability to execute commands with high privileges on the device. Given the 9.8 CVSS score, this represents a major threat to network integrity, allowing for potential man-in-the-middle attacks or total network traffic interception.

Remediation Plan

Immediate Action: Disable UPnP and remote management features immediately, and apply available firmware updates.

Proactive Monitoring: Review system logs for suspicious process execution or unexpected configuration changes.

Compensating Controls: Use a firewall to block external access to the device's web management interface.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of April 27, 2026, a public exploit is available, making this a high-risk vulnerability. Urgent remediation is recommended.

Analyst Recommendation

Organizations utilizing the Totolink A8000RU must treat this as a critical security incident. The presence of public exploits necessitates immediate isolation of the device from untrusted networks until a secure firmware version can be deployed.

---METADATA---
VENDOR: NASA-AMMOS
PRODUCT: plandev (sequencing-server)
AFFECTED_VERSIONS: 0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The NASA-AMMOS plandev sequencing-server contains an authentication bypass flaw in the session role derivation middleware, allowing unauthenticated attackers to perform unauthorized administrative actions.

Executive Summary:
A critical authentication bypass in the NASA-AMMOS plandev sequencing-server allows unauthenticated attackers to inject arbitrary expansion rules and modify command dictionaries.

Vulnerability Details

CVE-ID: CVE-2026-71214

Affected Software: NASA-AMMOS plandev (sequencing-server)

Affected Versions: 0

Vulnerability: The application incorrectly trusts client-supplied JSON request bodies to derive authorization roles, bypassing the intended JWT-based authentication. This allows unauthenticated users to impersonate administrative roles and perform unauthorized writes to command expansion rules and dictionaries.

Business Impact

This vulnerability carries a CVSS score of 9.8 and allows for the manipulation of sequencing rules that govern spacecraft activities. Unauthorized modification of these rules or command dictionaries could result in significant operational disruption, data integrity loss, and potential safety risks to associated hardware operations.

Remediation Plan

Immediate Action: Update the sequencing-server component to the latest version provided by NASA-AMMOS. Review the vendor security advisory to verify if specific configuration changes are required in addition to the software update.

Proactive Monitoring: Review application access logs for requests to /command-expansion/put-expansion or /put-dictionary that lack valid Authorization headers or show anomalous session_variables.

Compensating Controls: Implement strict network-level access controls to ensure only known, authorized clients can reach the sequencing-server endpoints.

Exploitation Status

Public Exploit Available: No (exploit_available unknown).

Analyst Notes: As of Aug 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is highly severe because it permits unauthorized modification of critical system logic without requiring authentication.

Analyst Recommendation

Given the critical nature of the sequencing-server and the risk posed by arbitrary command expansion, immediate patching is required. Organizations should treat this as a high-priority remediation to ensure the integrity of sequencing operations.

---METADATA---
VENDOR: Typemill
PRODUCT: Typemill
AFFECTED_VERSIONS: 0 through 2.25.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
Typemill's login endpoint lacks rate-limiting or account lockout mechanisms when the captcha is disabled, allowing for potential brute-force attacks.

Executive Summary:
A lack of authentication rate-limiting in Typemill versions up to 2.25.0 creates a high risk of unauthorized account access through brute-force attacks.

Vulnerability Details

CVE-ID: CVE-2026-71213

Affected Software: Typemill Typemill

Affected Versions: 0 through 2.25.0

Vulnerability: This is an improper restriction of excessive authentication attempts (CWE-307) occurring within the ControllerWebAuth login function. The vulnerability is exploitable by unauthenticated remote attackers.

Business Impact

The absence of account lockout or rate-limiting measures significantly increases the risk of successful credential stuffing or brute-force attacks against administrative or user accounts. With a CVSS score of 8.1, this vulnerability is considered High severity, as it could lead to full unauthorized access to the application and sensitive data compromise.

Remediation Plan

Immediate Action: Ensure the CAPTCHA feature is enabled in the Typemill configuration to mitigate automated login attempts while awaiting a formal security patch.

Proactive Monitoring: Review web access logs for high volumes of POST requests to the /tm/login endpoint originating from single or suspicious IP addresses.

Compensating Controls: Implement a Web Application Firewall (WAF) rule to rate-limit requests to the login endpoint and block IP addresses exhibiting aggressive authentication patterns.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable due to the default configuration lacking protective barriers against automated login attempts.

Analyst Recommendation

Given the High severity score, administrators must prioritize securing the authentication process immediately. Enabling the CAPTCHA is a vital, non-disruptive step to prevent account takeover attempts until an official update providing robust rate-limiting is released.

---METADATA---
VENDOR: Totolink
PRODUCT: A8000RU
AFFECTED_VERSIONS: 7.1cu.643_b20200521
---END_METADATA---

Description Summary:
A remote OS command injection vulnerability in the Totolink A8000RU CGI handler allows unauthenticated attackers to execute arbitrary commands via the wizard parameter.

Executive Summary:
A critical OS command injection vulnerability in the Totolink A8000RU router allows unauthenticated remote attackers to gain full system control.

Vulnerability Details

CVE-ID: CVE-2026-7121

Affected Software: Totolink A8000RU

Affected Versions: 7.1cu.643_b20200521

Vulnerability: This is an OS command injection vulnerability within the setWizardCfg function of the /cgi-bin/cstecgi.cgi component. The application fails to sanitize the wizard argument, allowing an unauthenticated remote attacker to inject and execute arbitrary system commands.

Business Impact

The vulnerability allows for full remote compromise of the device, which could be used as a pivot point into the local network. With a CVSS score of 9.8, the risk of complete device takeover and subsequent lateral movement is severe.

Remediation Plan

Immediate Action: Disconnect the affected device from the internet or apply the latest manufacturer firmware patch if available.

Proactive Monitoring: Monitor network traffic for unusual outbound connections or shell-like activity originating from the router.

Compensating Controls: Restrict management interface access to trusted IP addresses only via firewall rules.

Exploitation Status

Public Exploit Available: Yes

Analyst Notes: As of April 27, 2026, a public exploit is available, significantly increasing the probability of exploitation. Immediate action is required to secure the device.

Analyst Recommendation

Due to the availability of public exploit code and the critical nature of the vulnerability, immediate mitigation is required. If a firmware update is not available, the device should be isolated from external network access to prevent compromise.

---METADATA---
VENDOR: mrswapnilsahu
PRODUCT: Stock-Inventory-Management-System
AFFECTED_VERSIONS: 0 through 1.0
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
The Stock-Inventory-Management-System contains a SQL injection vulnerability and hardcoded credentials in the login module, allowing for total authentication bypass by unauthenticated remote attackers.

Executive Summary:
This critical vulnerability in the Stock-Inventory-Management-System allows unauthenticated remote attackers to gain full administrative access via SQL injection or hardcoded credentials.

Vulnerability Details

CVE-ID: CVE-2026-71207

Affected Software: mrswapnilsahu Stock-Inventory-Management-System

Affected Versions: 0 through 1.0

Vulnerability: The application is susceptible to SQL injection due to improper sanitization of login parameters, which is compounded by the presence of hardcoded administrative credentials. An unauthenticated attacker can leverage these flaws to bypass security controls entirely.

Business Impact

A successful exploit grants an attacker unrestricted administrative access to the inventory system. This could lead to the complete compromise of sensitive inventory data, unauthorized modification of records, and potential system-wide disruption, justifying the critical CVSS score of 9.8.

Remediation Plan

Immediate Action: Update to the latest version of the application as soon as the vendor provides a patch. In the interim, restrict access to the login interface using network-level controls.

Proactive Monitoring: Review application access logs for anomalous login patterns or SQL syntax characters in authentication fields.

Compensating Controls: Implement a Web Application Firewall (WAF) with SQL injection protection rules to block malicious payloads targeting the login module.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of Aug 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The presence of hardcoded credentials makes this software inherently insecure, and immediate replacement or isolation is advised.

Analyst Recommendation

Given the critical nature of this vulnerability and the ease of exploitation through trivial SQL injection or known credentials, organizations should prioritize the removal or patching of this software. Immediate action is required to prevent unauthorized access and potential data exfiltration.

---METADATA---
VENDOR: go-shiori
PRODUCT: shiori
AFFECTED_VERSIONS: 1.6.0 and 1.6.1
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
Shiori versions 1.6.0 and 1.6.1 contain an authentication bypass vulnerability in the CheckToken function due to improperly secured v1 API endpoints.

Executive Summary:
An authentication bypass vulnerability in Shiori 1.6.0 and 1.6.1 allows unauthorized access due to incomplete security logic in v1 API endpoints.

Vulnerability Details

CVE-ID: CVE-2026-71206

Affected Software: go-shiori shiori

Affected Versions: 1.6.0 and 1.6.1

Vulnerability: The vulnerability exists in the CheckToken function, where new v1 API endpoints were exposed with incomplete security controls. This allows an attacker to bypass standard authentication requirements.

Business Impact

With a CVSS score of 8.2, this vulnerability poses a significant risk of unauthorized access to the Shiori instance. An attacker could potentially access, modify, or delete bookmarked content or other sensitive data stored within the application, leading to a loss of data integrity and confidentiality.

Remediation Plan

Immediate Action: Upgrade all instances of Shiori to version 1.6.2 or later to resolve the authentication logic flaw.

Proactive Monitoring: Review application access logs for unusual patterns or access attempts to v1 API endpoints by unauthorized accounts.

Compensating Controls: Place the Shiori application behind a VPN or reverse proxy that requires secondary authentication before reaching the application layer.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of August 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The vulnerability is limited to the specific API implementation flaws introduced in the affected versions.

Analyst Recommendation

Users of the Shiori bookmarking application should update to version 1.6.2 immediately. The presence of an authentication bypass in an application designed to store user data necessitates prompt attention to maintain the security of the bookmarking environment.

---METADATA---
VENDOR: OpenStack
PRODUCT: Swift
AFFECTED_VERSIONS: 1.9.1 up to (excluding) 2.35.4, 2.36.0 up to (excluding) 2.36.3, 2.37.0 up to (excluding) 2.37.3, 2.38.0
CONFIDENCE: high
MISSING: none
---END_METADATA---

Description Summary:
OpenStack Swift contains an inefficient regular expression complexity vulnerability that can be exploited by unauthenticated remote attackers to cause a denial of service.

Executive Summary:
OpenStack Swift is vulnerable to a denial of service attack via inefficient regular expression complexity, which may lead to significant system resource exhaustion.

Vulnerability Details

CVE-ID: CVE-2026-71190

Affected Software: OpenStack Swift

Affected Versions: 1.9.1 up to (excluding) 2.35.4, 2.36.0 up to (excluding) 2.36.3, 2.37.0 up to (excluding) 2.37.3, 2.38.0

Vulnerability: The software is susceptible to CWE-1333, which involves inefficient regular expression complexity. An unauthenticated remote attacker can supply specifically crafted input to trigger high CPU consumption, resulting in a denial of service condition.

Business Impact

Exploitation of this vulnerability leads to service unavailability, which can severely impact business operations that rely on the Swift object storage service. With a CVSS score of 8.7, this vulnerability poses a high risk to service continuity and platform stability.

Remediation Plan

Immediate Action: Upgrade to the patched versions (2.35.4, 2.36.3, 2.37.3, or later as applicable) provided by the OpenStack project.

Proactive Monitoring: Monitor resource utilization, specifically CPU spikes on Swift nodes, which may indicate an ongoing denial of service attempt.

Compensating Controls: Deploy a Web Application Firewall or rate-limiting middleware to inspect and filter incoming requests for patterns that match known complex regular expression attacks.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 5, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently problematic as it allows remote attackers to disrupt services without authentication.

Analyst Recommendation

Given the potential for service disruption, organizations should schedule and apply the necessary patches as soon as possible. Maintaining service uptime is critical, and this update is essential for protecting the availability of OpenStack Swift.

---METADATA---
VENDOR: Highland Software
PRODUCT: Custom Role Manager
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
The Highland Software Custom Role Manager plugin for WordPress is susceptible to privilege escalation, allowing unauthorized users to obtain elevated permissions.

Executive Summary:
A privilege escalation vulnerability in the Highland Software Custom Role Manager plugin for WordPress could allow an authenticated attacker to gain administrative control over the site.

Vulnerability Details

CVE-ID: CVE-2026-7106

Affected Software: Highland Software Custom Role Manager

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: The plugin lacks proper capability checks during role management operations. An attacker with standard user access can exploit this flaw to modify user roles and escalate their privileges to administrator.

Business Impact

With a CVSS score of 8.8, this is a high-severity vulnerability. Successful exploitation grants an attacker full control over the WordPress site, allowing them to install malicious plugins, exfiltrate data, or modify site content, causing massive reputational and operational damage.

Remediation Plan

Immediate Action: Update the Custom Role Manager plugin to the latest version. If no update is available, deactivate and remove the plugin immediately.

Proactive Monitoring: Review WordPress user account logs for unexpected role changes or new administrative accounts.

Compensating Controls: Enforce strict WordPress security settings, including the use of strong passwords and multi-factor authentication for all administrative accounts.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of privilege escalation flaws, the potential for exploitation is high.

Analyst Recommendation

WordPress administrators must prioritize the update of this plugin. Given the risk of total site compromise, if an update is not immediately available, the plugin should be disabled until a secure version is released to ensure the security of the site's administration.

---METADATA---
VENDOR: Tenda
PRODUCT: F456
AFFECTED_VERSIONS: 1.0.0.5
CONFIDENCE: high
MISSING: patch
---END_METADATA---

Description Summary:
A buffer overflow vulnerability exists in Tenda F456 firmware version 1.0.0.5, which may allow for memory corruption and potential system compromise.

Executive Summary:
A critical memory corruption vulnerability in Tenda F456 firmware allows authenticated attackers to trigger a buffer overflow, potentially leading to unauthorized code execution.

Vulnerability Details

CVE-ID: CVE-2026-7101

Affected Software: Tenda F456

Affected Versions: 1.0.0.5

Vulnerability: This vulnerability consists of a buffer overflow and memory corruption (CWE-120/CWE-119) triggered via network-based input, requiring low-privileged user authentication to exploit.

Business Impact

Successful exploitation of this buffer overflow could lead to a crash or, more severely, the execution of arbitrary code with the privileges of the device's firmware. Given the CVSS score of 8.8, this poses a significant risk to the integrity and availability of the networking hardware, potentially allowing attackers to maintain persistence or intercept traffic.

Remediation Plan

Immediate Action: Check the Tenda support portal for available firmware updates; if no patch is available, restrict management access to the device to trusted administrative hosts only.

Proactive Monitoring: Monitor network traffic for unusual patterns or unexpected device reboots, which may indicate crash-based exploitation attempts.

Compensating Controls: Implement strict network access control lists (ACLs) to prevent unauthorized users from reaching the device management interface.

Exploitation Status

Public Exploit Available: No confirmed public exploit available.

Analyst Notes: As of May 29, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability requires authenticated access, which somewhat limits the immediate attack surface for external actors.

Analyst Recommendation

While this vulnerability requires authentication, the potential for memory corruption makes it a high-risk item. Administrators should prioritize updating the firmware to the latest version as soon as a vendor patch is released and enforce strict access controls in the interim.

---METADATA---
VENDOR: SourceCodester
PRODUCT: Pharmacy Sales and Inventory System
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability exists in the SourceCodester Pharmacy Sales and Inventory System 1, potentially exposing the application to unauthorized exploitation.

Executive Summary:
The SourceCodester Pharmacy Sales and Inventory System 1 contains a high-severity vulnerability that poses a significant risk of unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-7088

Affected Software: SourceCodester Pharmacy Sales and Inventory System

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability exists within the Pharmacy Sales and Inventory System, potentially allowing for unauthorized manipulation of data or system functions. The flaw indicates a weakness in the security architecture of the application.

Business Impact

Exploitation of this vulnerability could lead to severe consequences, including the theft of sensitive inventory information and the disruption of business operations. With a CVSS score of 7.3, the high severity justifies immediate attention to protect against potential unauthorized access.

Remediation Plan

Immediate Action: Update the Pharmacy Sales and Inventory System to the latest version provided by the vendor.

Proactive Monitoring: Review application logs for suspicious patterns or unauthorized attempts to access inventory management features.

Compensating Controls: Use a Web Application Firewall (WAF) to provide virtual patching and block malicious traffic that targets this identified vulnerability.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

It is critical that organizations using this software prioritize the installation of security updates. Failure to remediate this High-severity vulnerability may leave the system open to compromise; ensure all patches are applied as soon as they are made available by the vendor.

---METADATA---
VENDOR: SourceCodester
PRODUCT: Pharmacy Sales and Inventory System
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability exists in the SourceCodester Pharmacy Sales and Inventory System 1, potentially exposing the application to unauthorized exploitation.

Executive Summary:
The SourceCodester Pharmacy Sales and Inventory System 1 contains a high-severity vulnerability that poses a significant risk of unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-7087

Affected Software: SourceCodester Pharmacy Sales and Inventory System

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the Pharmacy Sales and Inventory System, likely involving insufficient validation of user-supplied input. Such weaknesses can often be exploited to gain unauthorized access or influence application logic.

Business Impact

Successful exploitation could result in the compromise of sensitive pharmacy inventory data and sales records. Given the CVSS score of 7.3, this vulnerability represents a significant risk to the business, potentially leading to unauthorized data disclosure or service disruption.

Remediation Plan

Immediate Action: Check for and install all relevant security updates and patches for the Pharmacy Sales and Inventory System.

Proactive Monitoring: Monitor database and application logs for unusual transaction activity or unauthorized access attempts.

Compensating Controls: Implement network-level access controls and WAF rules to prevent unauthorized users from interacting with the application's sensitive endpoints.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Security teams should act immediately to mitigate this vulnerability. Applying the vendor's patch is the primary requirement for reducing risk and protecting the integrity of the inventory and sales environment.

---METADATA---
VENDOR: itsourcecode
PRODUCT: Courier Management System
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability exists in the itsourcecode Courier Management System 1, potentially exposing the application to unauthorized exploitation.

Executive Summary:
The itsourcecode Courier Management System 1 contains a high-severity vulnerability that poses a significant risk of unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-7077

Affected Software: itsourcecode Courier Management System

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability resides within the Courier Management System, potentially allowing for unauthorized interaction with the application's backend. The flaw suggests a failure in security controls that could be abused by an attacker to affect system integrity.

Business Impact

Exploitation of this vulnerability could lead to unauthorized access to courier data and potential service interruption. The CVSS score of 7.3 highlights the necessity of addressing this flaw to maintain the confidentiality and integrity of management operations.

Remediation Plan

Immediate Action: Apply all security updates and patches released by the vendor to address this vulnerability.

Proactive Monitoring: Continuously review application logs for signs of unauthorized access or exploitation attempts targeting the management system.

Compensating Controls: Deploy Web Application Firewall (WAF) rules to detect and block malicious traffic patterns directed at the vulnerable components.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Administrators must prioritize the remediation of this vulnerability to ensure the security of their infrastructure. Prompt application of vendor-supplied patches is essential to mitigate the high-severity risk presented by this flaw.

---METADATA---
VENDOR: itsourcecode
PRODUCT: Courier Management System
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability exists in the itsourcecode Courier Management System 1, potentially exposing the application to unauthorized exploitation.

Executive Summary:
The itsourcecode Courier Management System 1 contains a high-severity vulnerability that poses a significant risk of unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-7076

Affected Software: itsourcecode Courier Management System

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the core functionality of the Courier Management System. The flaw likely involves an input validation or logic error that could be leveraged by an attacker to manipulate system processes.

Business Impact

A successful exploit could result in the compromise of logistics data, service disruption, and unauthorized access to backend administrative functions. With a CVSS score of 7.3, the vulnerability is classified as High, necessitating prompt remediation to prevent potential data exfiltration or operational downtime.

Remediation Plan

Immediate Action: Verify the version of the Courier Management System in use and apply all available security patches provided by the vendor.

Proactive Monitoring: Monitor application logs for anomalous database queries or unusual administrative activity that could indicate an exploitation attempt.

Compensating Controls: Utilize a Web Application Firewall (WAF) to block suspicious requests and mitigate the risk of exploitation while testing and deploying patches.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Security teams should treat this vulnerability as a high priority. Immediate patching is the most effective way to mitigate this risk; if a patch is not yet available, restrict access to the application to authorized network segments only.

---METADATA---
VENDOR: itsourcecode
PRODUCT: Construction Management System
AFFECTED_VERSIONS: See vendor advisory for specific affected versions
---END_METADATA---

Description Summary:
A security vulnerability exists in the itsourcecode Construction Management System 1, potentially exposing the application to unauthorized exploitation.

Executive Summary:
The itsourcecode Construction Management System 1 contains a high-severity vulnerability that poses a significant risk of unauthorized system access.

Vulnerability Details

CVE-ID: CVE-2026-7075

Affected Software: itsourcecode Construction Management System

Affected Versions: See vendor advisory for specific affected versions

Vulnerability: This vulnerability affects the core functionality of the Construction Management System. While specific vector details are currently limited, such flaws in similar systems often involve improper input validation or authentication handling.

Business Impact

Successful exploitation of this vulnerability could lead to unauthorized data access, potential system compromise, and significant disruption of project management operations. With a CVSS score of 7.3, this flaw is categorized as High, indicating that it could facilitate a breach of sensitive business information if left unpatched.

Remediation Plan

Immediate Action: Identify all instances of the affected software and apply the latest security updates provided by the vendor.

Proactive Monitoring: Review web server and application access logs for unusual patterns or unauthorized connection attempts targeting the management system.

Compensating Controls: Implement Web Application Firewall (WAF) rules to filter suspicious traffic and block common attack vectors directed at the application's interface.

Exploitation Status

Public Exploit Available: false

Analyst Notes: As of April 27, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the High severity rating, administrators must prioritize the assessment of this system within their environment. It is strongly recommended to apply all available patches immediately and ensure that the application is not exposed to the public internet without adequate security controls.