SGRC Daily Cyber Brief - 19 Nov 2026
SGRC-DCB-20261119Last updated Sources checked
Bottom line
- Findings
- 696
- 107 critical, 265 high, 257 medium, 33 low, 32 not yet scored, 1 incident, 1 campaign report
- On CISA's Known Exploited Vulnerabilities list
- 5
- CISA has evidence attackers are using them
- Fix available
- 116
- of 372 critical and high CVEs checked for a fix: 88 of 107 critical, 28 of 265 high
- Incident
- 1
- reported by BleepingComputer, not yet confirmed
- Campaign report
- 1
- from Google Cloud Blog
- Vulnerabilities. 45 are reported exploited by a cited source and not yet on CISA's list. 1 has passed the US federal due date. The oldest was November 18, 2026. The next US federal due date is November 21, 2026.
- Fix status. For the other CVEs, open the row for the vendor's advisory and, when the record states one, where the affected range ends. Confirm the fixed version there before patching.
- All CVEs. NVD published 689 CVEs from November 18, 2026 at 12:00 a.m. EST to November 19, 2026 at 12:00 a.m. EST, not counting rejected records. Findings also includes 5 CVEs that are not in this list, checked November 19, 2026 at 12:00 a.m. EST.
Findings
Showing 1–100 of 696 rows
Sorted by Risk order.
Number 1CVE-2024-27834Apple (multiple products)An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication.CVSS 5.5EPSS 1.5%Deadline passedCISA due Nov 18, 2026, passed
What happened
An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication.
Who can attack it
Someone with access to the system it runs on, such as at the keyboard or in a remote session like SSH. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by NIST.
How to fix
- Upgrade to the fixed release for your product and branch (fixed versions per the NVD record): safari: 17.5; ipados: 16.7.8 or 17.5; iphone os: 16.7.8 or 17.5; macos: 14.5; tvos: 17.5; watchos: 10.5; webkitgtk: 2.44.2; wpe webkit: 2.44.2. The NVD record lists no fixed version for fedora 39, 40.
- Statement in the NVD description: This issue is fixed in Safari 17.5, iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, watchOS 10.5.
- CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-18.
- Follow the vendor advisory: https://support.apple.com/en-us/120896
Affected versions
- before 17.5
- before 16.7.8
- 17.0 up to, not including, 17.5
- before 14.5
- before 10.5
- before 2.44.2
- 39
- 40
Risk record
- Response
- Immediate
- Added to KEV
- Nov 4, 2026
Sources
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- Apple (opens in a new tab)
- NVD API (opens in a new tab)
- CVE Program (opens in a new tab)
- CISA KEV (opens in a new tab)
- GitHub Advisory Database (opens in a new tab)
- OSV (opens in a new tab)
Number 2CVE-2024-10441Synology DiskStation Manager (DSM)Improper encoding or escaping of output vulnerability in the system plugin daemon in Synology BeeStation OS (BSM) before 1.1-65374 and Synology DiskStation Manager (DSM) before 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1 allows remote attackers to execute arbitrary code via unspecified vectors.CVSS 9.8EPSS 1.3%Deadline aheadCISA due Nov 21, 2026
What happened
Improper encoding or escaping of output vulnerability in the system plugin daemon in Synology BeeStation OS (BSM) before 1.1-65374 and Synology DiskStation Manager (DSM) before 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1 allows remote attackers to execute arbitrary code via unspecified vectors.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade to the fixed release for your product and branch (per Synology SA-24:20 and SA-24:23 and the CVE record): DiskStation Manager 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 or 7.1.1-42962-7 or above; BeeStation OS (BSM) 1.1-65374 or above, for BeeStation OS 1.1 and 1.0.
- CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-21.
- Follow the vendor advisory: https://www.synology.com/en-global/security/advisory/Synology_SA_24_20
Affected versions
- before 1.1-65374
- 7.2.2 up to, not including, 7.2.2-72806-1
- 7.2.1 up to, not including, 7.2.1-69057-6
- 7.2 up to, not including, 7.2-64570-4
- 7.1 up to, not including, 7.1.1-42962-7
Fixed versions
- 1.1-65374
- 7.2.2-72806-1
- 7.2.1-69057-6
- 7.2-64570-4
- 7.1.1-42962-7
Risk record
- Response
- Immediate
- Added to KEV
- Nov 18, 2026
Sources
Number 3CVE-2026-90436Apache Axis** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. With a suitable class on the application's classpath this leads to remote code execution.CVSS 9.8EPSS 1.1%Deadline aheadCISA due Nov 21, 2026
What happened
** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation. With a suitable class on the application's classpath this leads to remote code execution.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Apache (CVE record): "As Axis 1 has been EOL we recommend you migrate to a different SOAP engine, such as Apache Axis 2/Java. Alternatively you could use a build of Axis with the patch from https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd applied. The Apache Axis project does not expect to create an Axis 1.x release fixing this problem."
- Fixed by commit 41f3b4e (patch commit in the CVE record; the records do not name its branch): https://github.com/apache/axis-axis1-java/commit/41f3b4e8d04e310ca81f86b92630ab2c11d608bd
- CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-21.
- Follow the vendor advisory: https://lists.apache.org/thread.html/8slf0j9gz35z56t0glt5h0ncwlbn4bdz
Affected versions
- through 1.4
Risk record
- Response
- Immediate
- Added to KEV
- Nov 18, 2026
Sources
Number 4CVE-2026-90817Vanderbilt University Research Electronic Data Capture (REDCap)An unauthenticated Remote Code Execution vulnerability was found in the survey passthrough routing and Data Import processing logic, in which a malicious user could potentially exploit it by manipulating HTTP requests to access an unintended controller route from a public survey context and by supplying a crafted file-path/stream parameter during import handling. If successfully exploited, this could allow the attacker to remotely execute arbitrary code on the REDCap server. The attacker does not have to be authenticated in order to exploit this, but exploitation requires knowledge of a valid public survey hash.CVSS 9.8EPSS 3.7%Deadline aheadCISA due Nov 21, 2026
What happened
An unauthenticated Remote Code Execution vulnerability was found in the survey passthrough routing and Data Import processing logic, in which a malicious user could potentially exploit it by manipulating HTTP requests to access an unintended controller route from a public survey context and by supplying a crafted file-path/stream parameter during import handling. If successfully exploited, this could allow the attacker to remotely execute arbitrary code on the REDCap server. The attacker does not have to be authenticated in order to exploit this, but exploitation requires knowledge of a valid public survey hash.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Vendor solution (CVE record): Upgrade to REDCap 16.0.49 LTS, 17.3.10 LTS, or 17.4.4 Standard Release, as applicable.
- CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-11-21.
Affected versions
- 13.3.0
Fixed versions
- 16.0.49
- 17.3.10
- 17.4.4
Risk record
- Response
- Immediate
- Added to KEV
- Nov 18, 2026
Sources
Number 5CVE-2026-40217BerriAI LiteLLMLiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.CVSS 8.8EPSS 17.0%Deadline aheadCISA due Dec 2, 2026
What happened
LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade the pip package litellm to 1.83.10 or later (patched version per GitHub Advisory Database and OSV). The advisory's Patches section says: "Fixed in **`1.83.11`**. The hand-rolled sandbox has been replaced with `RestrictedPython`. Upgrade to `1.83.11` or later." and lists "Patched release: v1.83.10-stable"; the two differ, so use 1.83.11 or later if you can.
- CISA KEV required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Federal due date 2026-12-02.
- Third-party mitigation write-up: https://www.x41-dsec.de/lab/advisories/x41-2026-001-litellm/
If you cannot update yet: If upgrading is not immediately possible, block `POST /guardrails/test_custom_code` at your reverse proxy or API gateway.
Not a fix: the update is still required.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-40217.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.81.8 up to, not including, 1.83.10
Fixed versions
- 1.83.10
Risk record
- Response
- Immediate
- Added to KEV
- Nov 18, 2026
Sources
Number 6CVE-2012-20007TopThink ThinkPHPThinkPHP 2.0 through 2.2 and 3.0 Lite mode contains an eval injection vulnerability in the Dispatcher PATH_INFO parsing, which uses preg_replace with the /e modifier and a double-quoted replacement. Unauthenticated attackers can send crafted requests to index.php with a malicious 's' parameter containing PHP expressions to execute arbitrary code on the server.CVSS 9.8EPSS Not scoredReported exploitedCISA due None
What happened
ThinkPHP 2.0 through 2.2 and 3.0 Lite mode contains an eval injection vulnerability in the Dispatcher PATH_INFO parsing, which uses preg_replace with the /e modifier and a double-quoted replacement. Unauthenticated attackers can send crafted requests to index.php with a malicious 's' parameter containing PHP expressions to execute arbitrary code on the server.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
General guidance (MITRE CWE, not a vendor fix)
CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code). Phase: Architecture and Design, Implementation. If possible, refactor your code so that it does not need to use eval() at all.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-2-rce.yaml (community template; tests exposure, not compromise).
Affected versions
- 2.0 through 2.2
- 3.0
Risk record
- Response
- Immediate
Sources
Number 7CVE-2018-25443Baidu UEditorBaidu UEditor 1.4.0 through 1.4.3.3 contains an unrestricted file upload vulnerability in the catchimage action of /ueditor/net/controller.ashx that only validates the Content-Type header. Unauthenticated attackers can supply a source[] URL like x.jpg?.aspx to retain a malicious extension and write an executable .aspx file for remote code execution.CVSS 9.8EPSS Not scoredReported exploitedCISA due None
What happened
Baidu UEditor 1.4.0 through 1.4.3.3 contains an unrestricted file upload vulnerability in the catchimage action of /ueditor/net/controller.ashx that only validates the Content-Type header. Unauthenticated attackers can supply a source[] URL like x.jpg?.aspx to retain a malicious extension and write an executable .aspx file for remote code execution.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-17.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
General guidance (MITRE CWE, not a vendor fix)
CWE-434 (Unrestricted Upload of File with Dangerous Type). Phase: Architecture and Design. Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/ueditor-file-upload.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.4.0 through 1.4.3.3
Risk record
- Response
- Immediate
Sources
Number 8CVE-2019-25782TopThink ThinkPHPThinkPHP 5.0.0 before 5.0.24 contains a code injection vulnerability that allows unauthenticated attackers to execute commands by setting _method=__construct in POST data to overwrite the Request filter property. Attackers can send POST requests to endpoints reached via ?s=captcha or ?s=index/index/index with filter[]=system and server[REQUEST_METHOD] values to execute arbitrary system commands.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
ThinkPHP 5.0.0 before 5.0.24 contains a code injection vulnerability that allows unauthenticated attackers to execute commands by setting _method=__construct in POST data to overwrite the Request filter property. Attackers can send POST requests to endpoints reached via ?s=captcha or ?s=index/index/index with filter[]=system and server[REQUEST_METHOD] values to execute arbitrary system commands.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade TopThink ThinkPHP to 5.0.24 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/thinkphp/thinkphp-5023-rce.yaml (community template; tests exposure, not compromise).
Affected versions
- 5.0.0 up to, not including, 5.0.24
Fixed versions
- 5.0.24
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 9CVE-2021-48023Weaver Network Co., Ltd. E-cologyWeaver E-cology 9.0 contains an unrestricted file upload vulnerability in /page/exportImport/uploadOperation.jsp that allows unauthenticated attackers to upload arbitrary JSP files. Attackers can send a crafted multipart POST request with a JSP webshell written to /page/exportImport/fileTransfer/ to achieve remote code execution.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
Weaver E-cology 9.0 contains an unrestricted file upload vulnerability in /page/exportImport/uploadOperation.jsp that allows unauthenticated attackers to upload arbitrary JSP files. Attackers can send a crafted multipart POST request with a JSP webshell written to /page/exportImport/fileTransfer/ to achieve remote code execution.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-20.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
General guidance (MITRE CWE, not a vendor fix)
CWE-434 (Unrestricted Upload of File with Dangerous Type). Phase: Architecture and Design. Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/weaver/oa-v9-uploads-file.yaml (community template; tests exposure, not compromise).
Affected versions
- 9.0
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 10CVE-2021-48025Jiaxing Xiangtian Information Technology OpenSNSOpenSNS 3.2.1 contains an unauthenticated code injection vulnerability in the shareBox method of ShareController that allows attackers to invoke arbitrary model methods via the query parameter. Attackers can send crafted GET requests to /index.php?s=weibo/Share/shareBox abusing parse_str and ShareModel::getInfo to reach Schedule::runSchedule and execute code through assert.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
OpenSNS 3.2.1 contains an unauthenticated code injection vulnerability in the shareBox method of ShareController that allows attackers to invoke arbitrary model methods via the query parameter. Attackers can send crafted GET requests to /index.php?s=weibo/Share/shareBox abusing parse_str and ShareModel::getInfo to reach Schedule::runSchedule and execute code through assert.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
General guidance (MITRE CWE, not a vendor fix)
CWE-470 (Use of Externally-Controlled Input to Select Classes or Code). Phase: Architecture and Design. Refactor your code to avoid using reflection.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/opensns-rce.yaml (community template; tests exposure, not compromise).
Affected versions
- 3.2.1
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 11CVE-2022-51027FIT2CLOUD MeterSphereMeterSphere versions 1.13.0 before 1.14.7 and 1.15.0 before 1.16.4 contain a pre-authentication code injection vulnerability due to the /plugin/** endpoints being exposed with anonymous access. Attackers can upload a malicious jar via POST /plugin/add and invoke it through POST /plugin/customMethod using the 'entry' and 'request' parameters, which are passed to Class.forName and method invocation for remote code execution.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
MeterSphere versions 1.13.0 before 1.14.7 and 1.15.0 before 1.16.4 contain a pre-authentication code injection vulnerability due to the /plugin/** endpoints being exposed with anonymous access. Attackers can upload a malicious jar via POST /plugin/add and invoke it through POST /plugin/customMethod using the 'entry' and 'request' parameters, which are passed to Class.forName and method invocation for remote code execution.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade FIT2CLOUD MeterSphere to the fixed release for your branch: 1.14.7, 1.16.4 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/metersphere/metersphere-plugin-rce.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.13.0 up to, not including, 1.14.7
- 1.15.0 up to, not including, 1.16.4
Fixed versions
- 1.14.7
- 1.16.4
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 12CVE-2023-54419cym1102 nginxWebUInginxWebUI 3.0.0 before 3.5.8 contains an authentication bypass vulnerability that allows unauthenticated attackers to reach the /AdminPage/conf/runCmd endpoint by using a case-variant path that evades the case-sensitive /adminPage/ login filter. Attackers can pass OS commands through the cmd parameter, which are executed via /bin/sh with insufficient filtering of & and $() characters, achieving remote code execution.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
nginxWebUI 3.0.0 before 3.5.8 contains an authentication bypass vulnerability that allows unauthenticated attackers to reach the /AdminPage/conf/runCmd endpoint by using a case-variant path that evades the case-sensitive /adminPage/ login filter. Attackers can pass OS commands through the cmd parameter, which are executed via /bin/sh with insufficient filtering of & and $() characters, achieving remote code execution.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade cym1102 nginxWebUI to 3.5.8 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nginxwebui-runcmd-rce.yaml (community template; tests exposure, not compromise).
Affected versions
- 3.0.0 up to, not including, 3.5.8
Fixed versions
- 3.5.8
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 13CVE-2023-54422iDocViewiDocView before 13.10.1_20231115 contains an unrestricted file upload vulnerability in the /html/2word endpoint that allows unauthenticated attackers to write arbitrary files by supplying a malicious url parameter. Attackers can send a crafted GET request with the url parameter to download linked resources with an unsanitized path and unblocked .jsp extension, achieving remote code execution.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
iDocView before 13.10.1_20231115 contains an unrestricted file upload vulnerability in the /html/2word endpoint that allows unauthenticated attackers to write arbitrary files by supplying a malicious url parameter. Attackers can send a crafted GET request with the url parameter to download linked resources with an unsanitized path and unblocked .jsp extension, achieving remote code execution.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-11-22.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade iDocView to 13.10.1_20231115 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/idoc/idocview-2word-fileupload.yaml (community template; tests exposure, not compromise).
Affected versions
- before 13.10.1_20231115
Fixed versions
- 13.10.1_20231115
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 14CVE-2026-126752dagu-org DaguDagu 1.23.0 before 2.0.0 defaults auth.mode to none, allowing unauthenticated attackers to execute OS commands through the /api/v2/dag-runs endpoint. Attackers can send a POST request with an inline spec defining steps containing arbitrary shell commands to achieve remote code execution.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
Dagu 1.23.0 before 2.0.0 defaults auth.mode to none, allowing unauthenticated attackers to execute OS commands through the /api/v2/dag-runs endpoint. Attackers can send a POST request with an inline spec defining steps containing arbitrary shell commands to achieve remote code execution.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2026-03-11.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dagu-org Dagu to 2.0.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/dagucloud/dagu/security/advisories/GHSA-6qr9-g2xw-cw92
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/dagu-rce.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.23.0 up to, not including, 2.0.0
Fixed versions
- 2.0.0
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 15CVE-2026-126755ArangoDBArangoDB before 3.12.11 contains an authentication bypass vulnerability caused by a parser differential between the raw path authentication gate and the URL-decoded dispatch logic. Attackers can send requests with a %5f-encoded leading underscore to endpoints like /_db/_system/%5fapi/simple/first-example to reach /_api/* actions as superuser without authentication.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
ArangoDB before 3.12.11 contains an authentication bypass vulnerability caused by a parser differential between the raw path authentication gate and the URL-decoded dispatch logic. Attackers can send requests with a %5f-encoded leading underscore to endpoints like /_db/_system/%5fapi/simple/first-example to reach /_api/* actions as superuser without authentication.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2026-09-16.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade ArangoDB to 3.12.11 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/arangodb/arangodb/security/advisories/GHSA-rrgq-978q-36mq
- Vendor guidance (advisory, not a fix): "After upgrading, rotate the `root` password and all other database user passwords, and rotate the JWT secret (or keyfile) on all servers, then restart. Upgrading alone does not invalidate credentials that may already have been read."
- Vendor guidance (advisory, not a fix): "A public, runnable proof of concept has been available since 2026-09-13 that chains this vulnerability with GHSA-rvhw-4hpw-9vrx into unauthenticated remote code execution as the `arangod` OS user (root in the official image)."
If you cannot update yet: Deployments that cannot upgrade immediately can set `--server.authentication-system-only false`, which requires authentication for every request path (including Foxx routes) and closes the bypass.
Not a fix: the update is still required.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/arangodb/arangodb-auth-bypass.yaml (community template; tests exposure, not compromise).
Affected versions
- before 3.12.11
Fixed versions
- 3.12.11
Risk record
- Response
- Immediate
- Also rated
- 9.8 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 16CVE-2026-131914Idunno AntiCsrfDeserialization of untrusted data in double-submit cookie vs. form field validation in Idunno.AntiCsrf versions through 0.9.1 Beta on ASP.NET allows remote unauthenticated attackers to execute code via object injection.CVSS 9.3EPSS Not scoredReported exploitedCISA due None
What happened
Deserialization of untrusted data in double-submit cookie vs. form field validation in Idunno.AntiCsrf versions through 0.9.1 Beta on ASP.NET allows remote unauthenticated attackers to execute code via object injection.
Exploitation report
“Active exploitation in the wild has been observed.”
Mandiant, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Mandiant advisory: "Idunno.AntiCsrf is a defunct open-source project last released as 0.9.1 Beta (official build dated December 2008) on the since-retired CodePlex platform, and has no active maintainer or official patch available. Organizations should discontinue use of Idunno.AntiCsrf (Idunno.AntiCsrf.dll) and replace it with an actively supported anti-CSRF alternative".
- Follow the vendor advisory: https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0048.md
General guidance (MITRE CWE, not a vendor fix)
CWE-502 (Deserialization of Untrusted Data). Phase: Operation. Use an application firewall that can detect attacks against this weakness.
Affected versions
- through 0.9.1.0
Risk record
- Response
- Immediate
Sources
Number 17CVE-2016-20105Lucee ServerLucee Server versions 5.0.0.0 before 5.3.4.46 contain an insecure default configuration that allows unauthenticated attackers to set the initial admin password via the first-run form on /lucee/admin/web.cfm and /lucee/admin/server.cfm. Attackers can access the 'New Password' set-password form before any password is configured to seize administrative control of the server.CVSS 9.2EPSS Not scoredReported exploitedCISA due None
What happened
Lucee Server versions 5.0.0.0 before 5.3.4.46 contain an insecure default configuration that allows unauthenticated attackers to set the initial admin password via the first-run form on /lucee/admin/web.cfm and /lucee/admin/server.cfm. Attackers can access the 'New Password' set-password form before any password is configured to seize administrative control of the server.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-24.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link. It also depends on specific conditions of how the system is deployed or running, such as a race the attacker must win or a place on the network path.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Lucee Server to 5.3.4.46 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/lucee-unset-credentials.yaml (community template; tests exposure, not compromise).
Affected versions
- 5.0.0.0 up to, not including, 5.3.4.46
Fixed versions
- 5.3.4.46
Risk record
- Response
- Immediate
Sources
Number 18CVE-2022-51034Tangshan Pingsheng Electronic Technology Development Co., Ltd. Reservoir Safety Supervision PlatformTangshan Pingsheng Reservoir Safety Supervision Platform builds through 2022-11-30 contain an unauthenticated SQL injection vulnerability in the simcardId parameter of /WebServices/SIMMaintainService.asmx/GetAllRechargeRecordsBySIMCardId. Attackers can send crafted POST requests with time-based MSSQL payloads to extract database information including user, version, and database name.CVSS 8.8EPSS Not scoredReported exploitedCISA due None
What happened
Tangshan Pingsheng Reservoir Safety Supervision Platform builds through 2022-11-30 contain an unauthenticated SQL injection vulnerability in the simcardId parameter of /WebServices/SIMMaintainService.asmx/GetAllRechargeRecordsBySIMCardId. Attackers can send crafted POST requests with time-based MSSQL payloads to extract database information including user, version, and database name.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/pingsheng-electronic-sqli.yaml (community template; tests exposure, not compromise).
Affected versions
- through 2022-11-30
Risk record
- Response
- Immediate
Sources
Number 19CVE-2012-20008OS4ED openSISopenSIS 5.1 before 9.0 contains a local file inclusion vulnerability that allows authenticated users to include arbitrary files through the modname parameter of ajax.php. Attackers can prefix a payload with misc/ and use ../ directory traversal to read sensitive files like /etc/passwd or execute local scripts in the web server context.CVSS 8.8EPSS Not scoredReported exploitedCISA due None
What happened
openSIS 5.1 before 9.0 contains a local file inclusion vulnerability that allows authenticated users to include arbitrary files through the modname parameter of ajax.php. Attackers can prefix a payload with misc/ and use ../ directory traversal to read sensitive files like /etc/passwd or execute local scripts in the web server context.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade OS4ED openSIS to 9.0 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/opensis-lfi.yaml (community template; tests exposure, not compromise).
Affected versions
- 5.1 up to, not including, 9.0
Fixed versions
- 9.0
Risk record
- Response
- Immediate
Sources
Number 20CVE-2016-20106NUUO NVRmini 2NUUO NVRmini 2 through 3.0.8 contains a file disclosure vulnerability that allows unauthenticated attackers to read web-root files by passing a filename to the 'css' parameter of css_parser.php. Attackers can retrieve PHP source files confined to the document root, exposing hardcoded credentials and sensitive application logic.CVSS 8.7EPSS Not scoredReported exploitedCISA due None
What happened
NUUO NVRmini 2 through 3.0.8 contains a file disclosure vulnerability that allows unauthenticated attackers to read web-root files by passing a filename to the 'css' parameter of css_parser.php. Attackers can retrieve PHP source files confined to the document root, exposing hardcoded credentials and sensitive application logic.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-17.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/nuuo-file-inclusion.yaml (community template; tests exposure, not compromise).
Affected versions
- through 3.0.8
Risk record
- Response
- Immediate
Sources
Number 21CVE-2022-51030Qibosoft QiboCMSQiboCMS V7 contains an arbitrary file download vulnerability in inc/job/download.php that allows unauthenticated attackers to read files by supplying a base64-encoded url parameter to /do/job.php?job=download. Attackers can bypass the .php extension check using the Windows 'ph<' wildcard to download sensitive files such as configuration files containing database credentials.CVSS 8.7EPSS Not scoredReported exploitedCISA due None
What happened
QiboCMS V7 contains an arbitrary file download vulnerability in inc/job/download.php that allows unauthenticated attackers to read files by supplying a base64-encoded url parameter to /do/job.php?job=download. Attackers can bypass the .php extension check using the Windows 'ph<' wildcard to download sensitive files such as configuration files containing database credentials.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/qibocms-file-download.yaml (community template; tests exposure, not compromise).
Affected versions
- V7
Risk record
- Response
- Immediate
Sources
Number 22CVE-2023-54418NuxtNuxt 3.0.0-rc.1 before 3.0.0-rc.13 contains an arbitrary file read vulnerability caused by the Vite dev server default setting vite.server.fs.strict=false. Unauthenticated attackers can request /_nuxt/@fs/<absolute path> with a raw query to read arbitrary files like /etc/passwd from the system.CVSS 8.7EPSS Not scoredReported exploitedCISA due None
What happened
Nuxt 3.0.0-rc.1 before 3.0.0-rc.13 contains an arbitrary file read vulnerability caused by the Vite dev server default setting vite.server.fs.strict=false. Unauthenticated attackers can request /_nuxt/@fs/<absolute path> with a raw query to read arbitrary files like /etc/passwd from the system.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-18.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade nuxt to 3.0.0-rc.13 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/nuxt/nuxt-js-lfi.yaml (community template; tests exposure, not compromise).
Affected versions
- 3.0.0-rc.1 up to, not including, 3.0.0-rc.13
Fixed versions
- 3.0.0-rc.13
Risk record
- Response
- Immediate
Sources
Number 23CVE-2018-25442Baidu UEditorBaidu UEditor 1.4.0 before 1.4.3.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to make arbitrary requests via the source[] parameter in /ueditor/jsp/controller.jsp?action=catchimage. Attackers can supply crafted URLs that the ImageHunter component fetches through url.openConnection() to reach internal services and bypass network restrictions.CVSS 8.3EPSS Not scoredReported exploitedCISA due None
What happened
Baidu UEditor 1.4.0 before 1.4.3.1 contains a server-side request forgery vulnerability that allows unauthenticated attackers to make arbitrary requests via the source[] parameter in /ueditor/jsp/controller.jsp?action=catchimage. Attackers can supply crafted URLs that the ImageHunter component fetches through url.openConnection() to reach internal services and bypass network restrictions.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-03.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Baidu UEditor to 1.4.3.1 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/ueditor/ueditor-ssrf.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.4.0 up to, not including, 1.4.3.1
Fixed versions
- 1.4.3.1
Risk record
- Response
- Immediate
Sources
Number 24CVE-2019-25784dayrui FineCMSFineCMS versions 5.0.4 before 5.0.11 contain an unauthenticated SQL injection vulnerability in the data2 API action handled by list_tag in libraries/Template.php. Attackers can send GET requests to index.php?c=api&m=data2 with a valid auth hash and the param action=sql sql='...' to execute arbitrary SELECT queries and extract database information.CVSS 8.2EPSS Not scoredReported exploitedCISA due None
What happened
FineCMS versions 5.0.4 before 5.0.11 contain an unauthenticated SQL injection vulnerability in the data2 API action handled by list_tag in libraries/Template.php. Attackers can send GET requests to index.php?c=api&m=data2 with a valid auth hash and the param action=sql sql='...' to execute arbitrary SELECT queries and extract database information.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dayrui FineCMS to 5.0.11 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/finecms-sqli.yaml (community template; tests exposure, not compromise).
Affected versions
- 5.0.4 up to, not including, 5.0.11
Fixed versions
- 5.0.11
Risk record
- Response
- Immediate
- Also rated
- 8.8 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 25CVE-2021-48021Chamilo LMSChamilo LMS 1.11.10 before 1.11.16 contains an unauthenticated SQL injection vulnerability in the searchOptionsFromTags function through the options parameter of extra_field.ajax.php. Attackers can send POST requests with a malicious JSON options array to inject SQL into the IN clause and extract database information.CVSS 8.2EPSS Not scoredReported exploitedCISA due None
What happened
Chamilo LMS 1.11.10 before 1.11.16 contains an unauthenticated SQL injection vulnerability in the searchOptionsFromTags function through the options parameter of extra_field.ajax.php. Attackers can send POST requests with a malicious JSON options array to inject SQL into the IN clause and extract database information.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Chamilo LMS to 1.11.16 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/chamilo-lms-sqli.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.11.10 up to, not including, 1.11.16
Fixed versions
- 1.11.16
Risk record
- Response
- Immediate
- Also rated
- 8.8 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 26CVE-2022-51028CmsEasyCmsEasy 7.7.5_20210919 contains an unauthenticated SQL injection vulnerability in the execsql_action function at /?case=crossall&act=execsql that executes attacker-supplied queries decrypted with the hardcoded key 'cmseasy_sql'. Attackers can send a crafted 'sql' parameter to run arbitrary SQL and dump the admin username and password hash.CVSS 8.2EPSS Not scoredReported exploitedCISA due None
What happened
CmsEasy 7.7.5_20210919 contains an unauthenticated SQL injection vulnerability in the execsql_action function at /?case=crossall&act=execsql that executes attacker-supplied queries decrypted with the hardcoded key 'cmseasy_sql'. Attackers can send a crafted 'sql' parameter to run arbitrary SQL and dump the admin username and password hash.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-22.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/cmseasy-crossall-act-sqli.yaml (community template; tests exposure, not compromise).
Affected versions
- 7.7.5_20210919
Risk record
- Response
- Immediate
- Also rated
- 8.8 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 27CVE-2024-58402DevWebister Azon DominatorAzon Dominator releases through 2024-06-03 contain an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries through the cid parameter in /fetch_products.php. Attackers can send crafted POST requests with boolean-based or time-based blind payloads to extract sensitive database information.CVSS 8.2EPSS Not scoredReported exploitedCISA due None
What happened
Azon Dominator releases through 2024-06-03 contain an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries through the cid parameter in /fetch_products.php. Attackers can send crafted POST requests with boolean-based or time-based blind payloads to extract sensitive database information.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/azon-dominator-sqli.yaml (community template; tests exposure, not compromise).
Affected versions
- through 2024-06-03
Risk record
- Response
- Immediate
- Also rated
- 8.8 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 28CVE-2019-25785FanRuan FineReportFineReport 8.0 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files through the resourcepath parameter of the /WebReport/ReportServer endpoint. Attackers can send GET requests with op=chart and cmd=get_geo_json to read sensitive files like privilege.xml and extract admin credentials.CVSS 7.5EPSS Not scoredReported exploitedCISA due None
What happened
FineReport 8.0 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files through the resourcepath parameter of the /WebReport/ReportServer endpoint. Attackers can send GET requests with op=chart and cmd=get_geo_json to read sensitive files like privilege.xml and extract admin credentials.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/finereport/finereport-path-traversal.yaml (community template; tests exposure, not compromise).
Affected versions
- 8.0
Risk record
- Response
- Immediate
- Also rated
- 8.7 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 29CVE-2021-48022Rocket.ChatRocket.Chat versions 0.61.0 before 3.11.4, 3.12.x before 3.12.4 and 3.13.x before 3.13.2 contain a missing authorization vulnerability allowing unauthenticated attackers to read any room's messages via the livechat:loadHistory Meteor method. Attackers can mint a guest token through livechat:registerGuest and send POST requests to /api/v1/method.callAnon with a target rid parameter to retrieve message history without membership checks.CVSS 7.5EPSS Not scoredReported exploitedCISA due None
What happened
Rocket.Chat versions 0.61.0 before 3.11.4, 3.12.x before 3.12.4 and 3.13.x before 3.13.2 contain a missing authorization vulnerability allowing unauthenticated attackers to read any room's messages via the livechat:loadHistory Meteor method. Attackers can mint a guest token through livechat:registerGuest and send POST requests to /api/v1/method.callAnon with a target rid parameter to retrieve message history without membership checks.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2025-02-13.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Rocket.Chat to the fixed release for your branch: 3.11.4, 3.12.4, 3.13.2 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/rocketchat/unauth-message-read.yaml (community template; tests exposure, not compromise).
Affected versions
- 0.61.0 up to, not including, 3.11.4
- 3.12.0 up to, not including, 3.12.4
- 3.13.0 up to, not including, 3.13.2
Fixed versions
- 3.11.4
- 3.12.4
- 3.13.2
Risk record
- Response
- Immediate
- Also rated
- 8.7 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 30CVE-2022-51029Synway SMG Gateway Management SoftwareSynway SMG Gateway Management Software builds through 2022-03-15 contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files via the downfile parameter in /down.php. Attackers can send a multipart POST request to /down.php with a traversal path in downfile to retrieve sensitive files like /etc/passwd.CVSS 7.5EPSS Not scoredReported exploitedCISA due None
What happened
Synway SMG Gateway Management Software builds through 2022-03-15 contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files via the downfile parameter in /down.php. Attackers can send a multipart POST request to /down.php with a traversal path in downfile to retrieve sensitive files like /etc/passwd.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-20.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/sanhui-smg-file-read.yaml (community template; tests exposure, not compromise).
Affected versions
- through 2022-03-15
Risk record
- Response
- Immediate
- Also rated
- 8.7 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 31CVE-2023-54417NuxtNuxt 3.0.0 before 3.4.2 contains a semi-arbitrary file read vulnerability in the vite-node dev server middleware that allows unauthenticated attackers to read files by supplying an absolute path as the moduleId. Attackers can send GET requests to /__nuxt_vite_node__/module/ with an absolute file path to read sensitive system files.CVSS 7.5EPSS Not scoredReported exploitedCISA due None
What happened
Nuxt 3.0.0 before 3.4.2 contains a semi-arbitrary file read vulnerability in the vite-node dev server middleware that allows unauthenticated attackers to read files by supplying an absolute path as the moduleId. Attackers can send GET requests to /__nuxt_vite_node__/module/ with an absolute file path to read sensitive system files.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade nuxt to 3.4.2 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/nuxt/nuxt-js-semi-lfi.yaml (community template; tests exposure, not compromise).
Affected versions
- 3.0.0 up to, not including, 3.4.2
Fixed versions
- 3.4.2
Risk record
- Response
- Immediate
- Also rated
- 8.7 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 32CVE-2023-54420Fujian Apex Software Co., Ltd. LiveBOSLiveBOS builds through 2023-08-16 contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files via the imgName parameter in /feed/ShowImage.do using a ';.js.jsp' suffix bypass. Attackers can send crafted GET requests with directory traversal sequences in imgName to read system files such as /etc/passwd.CVSS 7.5EPSS Not scoredReported exploitedCISA due None
What happened
LiveBOS builds through 2023-08-16 contain a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files via the imgName parameter in /feed/ShowImage.do using a ';.js.jsp' suffix bypass. Attackers can send crafted GET requests with directory traversal sequences in imgName to read system files such as /etc/passwd.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-30.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/livebos-file-read.yaml (community template; tests exposure, not compromise).
Affected versions
- through 2023-08-16
Risk record
- Response
- Immediate
- Also rated
- 8.7 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 33CVE-2024-58403Shanghai Aishu Information Technology Co., Ltd. AnyShareAnyShare builds through 2024-11 contain a missing authentication vulnerability in the /api/ShareMgnt/Usrm_GetAllUsers endpoint that exposes user records including password fields. Attackers can send unauthenticated POST requests with a [start,limit] body to retrieve usernames, passwords, and department information for all users.CVSS 7.5EPSS Not scoredReported exploitedCISA due None
What happened
AnyShare builds through 2024-11 contain a missing authentication vulnerability in the /api/ShareMgnt/Usrm_GetAllUsers endpoint that exposes user records including password fields. Attackers can send unauthenticated POST requests with a [start,limit] body to retrieve usernames, passwords, and department information for all users.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2024-12-25.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/aishu-anyshare-info-exposure.yaml (community template; tests exposure, not compromise).
Affected versions
- through 2024-11
Risk record
- Response
- Immediate
- Also rated
- 8.7 High under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 34CVE-2020-37290Kiwi TCMSKiwi TCMS before 8.6 contains a missing authorization vulnerability in the User.filter JSON-RPC method that allows unauthenticated attackers to retrieve user account information. Attackers can send a POST request to /json-rpc/ invoking User.filter with a query parameter to disclose sensitive user data without authentication.CVSS 6.9EPSS Not scoredReported exploitedCISA due None
What happened
Kiwi TCMS before 8.6 contains a missing authorization vulnerability in the User.filter JSON-RPC method that allows unauthenticated attackers to retrieve user account information. Attackers can send a POST request to /json-rpc/ invoking User.filter with a query parameter to disclose sensitive user data without authentication.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Kiwi TCMS to 8.6 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/kiwitcms-json-rpc.yaml (community template; tests exposure, not compromise).
Affected versions
- before 8.6
Fixed versions
- 8.6
Risk record
- Response
- Immediate
Sources
Number 35CVE-2021-48027Rother OSS OTOBOOTOBO 10.0.1 before 10.0.13 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users by supplying arbitrary URLs to the ExternalURLJump action. Attackers can craft GET requests to /otobo/index.pl?Action=ExternalURLJump with a malicious URL parameter, which the ExternalURLJump.pm module redirects to without an allow-list check, enabling phishing attacks.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
OTOBO 10.0.1 before 10.0.13 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users by supplying arbitrary URLs to the ExternalURLJump action. Attackers can craft GET requests to /otobo/index.pl?Action=ExternalURLJump with a malicious URL parameter, which the ExternalURLJump.pm module redirects to without an allow-list check, enabling phishing attacks.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Rother OSS OTOBO to 10.0.13 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/otobo-open-redirect.yaml (community template; tests exposure, not compromise).
Affected versions
- 10.0.1 up to, not including, 10.0.13
Fixed versions
- 10.0.13
Risk record
- Response
- Immediate
Sources
Number 36CVE-2022-51032Johnwarne reddit-top-rssReddit Top RSS through commit 5e38bfd contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the unescaped score GET parameter. Attackers can craft links with a score value that closes the input value attribute in html.php, executing JavaScript in victims' browsers.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
Reddit Top RSS through commit 5e38bfd contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the unescaped score GET parameter. Attackers can craft links with a score value that closes the input value attribute in html.php, executing JavaScript in victims' browsers.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/reddittop-rss-xss.yaml (community template; tests exposure, not compromise).
Risk record
- Response
- Immediate
Sources
Number 37CVE-2022-51033JoomBri CareersJoomBri Careers 3.3.0 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the 'keyword' parameter of the /for-jobseekers/search-jobs endpoint in com_jbcareers. Attackers can craft malicious URLs using an attribute-breakout payload with onfocus and autofocus to execute arbitrary JavaScript and steal session tokens or credentials.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
JoomBri Careers 3.3.0 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the 'keyword' parameter of the /for-jobseekers/search-jobs endpoint in com_jbcareers. Attackers can craft malicious URLs using an attribute-breakout payload with onfocus and autofocus to execute arbitrary JavaScript and steal session tokens or credentials.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/joomla/joomla-joombri-careers-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 3.3.0
Risk record
- Response
- Immediate
Sources
Number 38CVE-2023-54416Tiki Wiki CMS GroupwareTiki Wiki CMS Groupware 12.12 through 12.14, 15.5 before 18.10, 19.0 before 21.9, 22.0 before 24.3, and 25.0 contain a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the objectId parameter of tiki-ajax_services.php. Attackers can send a crafted GET request with the comment controller and list action to execute arbitrary JavaScript and steal session tokens or credentials.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
Tiki Wiki CMS Groupware 12.12 through 12.14, 15.5 before 18.10, 19.0 before 21.9, 22.0 before 24.3, and 25.0 contain a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the objectId parameter of tiki-ajax_services.php. Attackers can send a crafted GET request with the comment controller and list action to execute arbitrary JavaScript and steal session tokens or credentials.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/tikiwiki-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 12.12 through 12.14
- 15.5 up to, not including, 18.10
- 19.0 up to, not including, 21.9
- 22.0 up to, not including, 24.3
- 25.0 up to, not including, 25.1
Risk record
- Response
- Immediate
Sources
Number 39CVE-2023-54421phpLDAPadminphpLDAPadmin 1.1.0 before 1.2.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the dn parameter of cmd.php?cmd=template_engine. Attackers can supply an unparseable dn value that pretty_print_dn returns unescaped in the 'No such entry' error, executing JavaScript in victims' browsers.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
phpLDAPadmin 1.1.0 before 1.2.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the dn parameter of cmd.php?cmd=template_engine. Attackers can supply an unparseable dn value that pretty_print_dn returns unescaped in the 'No such entry' error, executing JavaScript in victims' browsers.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade phpLDAPadmin to 1.2.5 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/phpldapadmin-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 1.1.0 up to, not including, 1.2.5
Fixed versions
- 1.2.5
Risk record
- Response
- Immediate
Sources
Number 40CVE-2026-126753LimeSurveyLimeSurvey 6.5.0 before 6.16.11 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users by supplying arbitrary values to the url parameter. Attackers can send crafted GET requests to index.php?r=editorLink, where EditorLinkController concatenates url and route unvalidated, redirecting victims to attacker-controlled sites for phishing.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
LimeSurvey 6.5.0 before 6.16.11 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users by supplying arbitrary values to the url parameter. Attackers can send crafted GET requests to index.php?r=editorLink, where EditorLinkController concatenates url and route unvalidated, redirecting victims to attacker-controlled sites for phishing.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2026-03-20.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade LimeSurvey to 6.16.11 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/limesurvey/limesurvey-open-redirect.yaml (community template; tests exposure, not compromise).
Affected versions
- 6.5.0 up to, not including, 6.16.11
Fixed versions
- 6.16.11
Risk record
- Response
- Immediate
Sources
Number 41CVE-2026-126754cPanel, L.L.C. cPanel & WHMcPanel & WHM 11.134.0.13 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the mpidentity parameter of /mailman/listinfo. Attackers can send crafted requests with a script-context breakout payload in mpidentity to execute arbitrary JavaScript in the victim's browser.CVSS 6.1EPSS Not scoredReported exploitedCISA due None
What happened
cPanel & WHM 11.134.0.13 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the mpidentity parameter of /mailman/listinfo. Attackers can send crafted requests with a script-context breakout payload in mpidentity to execute arbitrary JavaScript in the victim's browser.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2026-06-08.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take some action first.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/cpanel/cpanel-mailman-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 11.134.0.13
Risk record
- Response
- Immediate
Sources
Number 42CVE-2019-25783Tiny RSSTiny Tiny RSS before commit c68ac04 (2019-03-03) contains an open redirect vulnerability that allows unauthenticated attackers to redirect users through the unvalidated 'return' parameter. Attackers can craft requests to /public.php?op=login with an absolute external URL in 'return', which is placed in the Location header to send victims to attacker-controlled sites.CVSS 5.3EPSS Not scoredReported exploitedCISA due None
What happened
Tiny Tiny RSS before commit c68ac04 (2019-03-03) contains an open redirect vulnerability that allows unauthenticated attackers to redirect users through the unvalidated 'return' parameter. Attackers can craft requests to /public.php?op=login with an absolute external URL in 'return', which is placed in the Location header to send victims to attacker-controlled sites.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2026-02-26.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user only has to take an ordinary step, such as viewing an altered web page.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Fixed by commit c68ac04 (patch commit in the CVE record; the records do not name its branch): https://github.com/tt-rss/tt-rss/commit/c68ac04020d85a296c784de18f8def3f365f9f6a
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/tinytiny-rss-redirect.yaml (community template; tests exposure, not compromise).
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 43CVE-2021-48026Beijing Zhongqing Modern Technology Zhongqing Naboo Education Cloud PlatformZhongqing Naboo Education Cloud Platform builds through 2021-07-09 contain a missing authentication vulnerability in the /api/TeacherQuery/SearchTeacherInSiteWithPagerRecords endpoint that allows unauthenticated attackers to access sensitive teacher data. Attackers can send unauthenticated GET requests to this endpoint to retrieve user names, login names, and admin ids from the JSON response.CVSS 5.3EPSS Not scoredReported exploitedCISA due None
What happened
Zhongqing Naboo Education Cloud Platform builds through 2021-07-09 contain a missing authentication vulnerability in the /api/TeacherQuery/SearchTeacherInSiteWithPagerRecords endpoint that allows unauthenticated attackers to access sensitive teacher data. Attackers can send unauthenticated GET requests to this endpoint to retrieve user names, login names, and admin ids from the JSON response.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-11-15.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
- The CVE record is tagged "exclusively-hosted-service". The CVE record schema defines it: "All known software and/or hardware affected by this CVE Record is known to exist only in the affected hosted service. If the vulnerability affects both hosted and on-prem software and/or hardware, then the tag should not be used." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/zqnb-educationcloud-exposure.yaml (community template; tests exposure, not compromise).
Affected versions
- through 2021-07-09
Risk record
- Response
- Immediate
- Also rated
- 6.9 Medium under CVSS 4.0, by disclosure@vulncheck.com
Sources
Number 44CVE-2021-48028Public Knowledge Project Open Journal SystemsOpen Journal Systems 2.1.0 before 3.0.0 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users to external domains by abusing the source parameter. Attackers can send GET requests to /index.php/index/user/setLocale/<locale> with a source value beginning with '@', which UserHandler.inc.php appends to the server host, redirecting victims to attacker-controlled sites for phishing.CVSS 5.3EPSS Not scoredReported exploitedCISA due None
What happened
Open Journal Systems 2.1.0 before 3.0.0 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users to external domains by abusing the source parameter. Attackers can send GET requests to /index.php/index/user/setLocale/<locale> with a source value beginning with '@', which UserHandler.inc.php appends to the server host, redirecting victims to attacker-controlled sites for phishing.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2024-12-05.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user only has to take an ordinary step, such as viewing an altered web page.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Public Knowledge Project Open Journal Systems to 3.0.0 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/pkp-lib-open-redirect.yaml (community template; tests exposure, not compromise).
Affected versions
- 2.1.0 up to, not including, 3.0.0
Fixed versions
- 3.0.0
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 45CVE-2010-20126Daniel K. Imori Virtual Keyboard plugin for SquirrelMailVirtual Keyboard plugin for SquirrelMail through 0.9.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject script by supplying unsanitized input in the passformname parameter. Attackers can craft GET requests to /plugins/vkeyboard/vkeyboard.php with script payloads in passformname to execute code in victims' browsers and steal session cookies.CVSS 5.1EPSS Not scoredReported exploitedCISA due None
What happened
Virtual Keyboard plugin for SquirrelMail through 0.9.1 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject script by supplying unsanitized input in the passformname parameter. Attackers can craft GET requests to /plugins/vkeyboard/vkeyboard.php with script payloads in passformname to execute code in victims' browsers and steal session cookies.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take a deliberate step, such as importing a file or accepting a security prompt.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/squirrelmail/squirrelmail-vkeyboard-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- through 0.9.1
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 46CVE-2019-25786SIR (gnuboard) gnuboard5Gnuboard5 5.0.1 before 5.3.3.3 and 5.4.0.1 before 5.4.0.2 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the arr_ajax_msg parameter. Attackers can craft GET requests to /plugin/sms5/ajax.sms_emoticon.php, where common.php's @extract($_GET) injects the value into the echoed JSON output, executing script in victims' browsers.CVSS 5.1EPSS Not scoredReported exploitedCISA due None
What happened
Gnuboard5 5.0.1 before 5.3.3.3 and 5.4.0.1 before 5.4.0.2 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts through the arr_ajax_msg parameter. Attackers can craft GET requests to /plugin/sms5/ajax.sms_emoticon.php, where common.php's @extract($_GET) injects the value into the echoed JSON output, executing script in victims' browsers.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take a deliberate step, such as importing a file or accepting a security prompt.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade SIR (gnuboard) gnuboard5 to the fixed release for your branch: 5.3.3.3, 5.4.0.2 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://sir.kr/g5_pds/4788
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/gnuboard/gnuboard-sms-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 5.0.1 up to, not including, 5.3.3.3
- 5.4.0.1 up to, not including, 5.4.0.2
Fixed versions
- 5.3.3.3
- 5.4.0.2
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 47CVE-2022-51031PMB Services PMBPMB 7.3.1 before 7.3.15 and 7.4.x before 7.4.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject script through unescaped POST parameter names. Attackers can send crafted parameter names to opac_css/index.php extended_search, which empr.inc.php and languages.inc.php reflect into hidden form inputs to execute JavaScript.CVSS 5.1EPSS Not scoredReported exploitedCISA due None
What happened
PMB 7.3.1 before 7.3.15 and 7.4.x before 7.4.5 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject script through unescaped POST parameter names. Attackers can send crafted parameter names to opac_css/index.php extended_search, which empr.inc.php and languages.inc.php reflect into hidden form inputs to execute JavaScript.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take a deliberate step, such as importing a file or accepting a security prompt.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade PMB Services PMB to the fixed release for your branch: 7.3.15, 7.4.5 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/pmb-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 7.3.1 up to, not including, 7.3.15
- 7.4.RC1 up to, not including, 7.4.5
Fixed versions
- 7.3.15
- 7.4.5
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 48CVE-2022-51035SLiMS Senayan Library Management SystemSLiMS Senayan Library Management System 9.4.0 before 9.4.2 contains a reflected cross-site scripting vulnerability in the destination parameter of /index.php?p=member, which is echoed unmodified into the login form action attribute. Unauthenticated attackers can craft a malicious destination value to inject script and hijack PHPSESSID sessions of victims who access the link.CVSS 5.1EPSS Not scoredReported exploitedCISA due None
What happened
SLiMS Senayan Library Management System 9.4.0 before 9.4.2 contains a reflected cross-site scripting vulnerability in the destination parameter of /index.php?p=member, which is echoed unmodified into the login form action attribute. Unauthenticated attackers can craft a malicious destination value to inject script and hijack PHPSESSID sessions of victims who access the link.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take a deliberate step, such as importing a file or accepting a security prompt.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade SLiMS Senayan Library Management System to 9.4.2 or later (fixed versions per the CVE record).
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/slims-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 9.4.0 up to, not including, 9.4.2
Fixed versions
- 9.4.2
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 49CVE-2024-58401Webkul BagistoBagisto 2.1.0 before 2.2.1 contains a client-side template injection vulnerability in the search page where the 'query' parameter is rendered unescaped inside a Vue app root. Unauthenticated attackers can send crafted VueJS template expressions to the /bagisto-common/search endpoint via the 'query' parameter to execute arbitrary JavaScript in victims' browsers.CVSS 5.1EPSS Not scoredReported exploitedCISA due None
What happened
Bagisto 2.1.0 before 2.2.1 contains a client-side template injection vulnerability in the search page where the 'query' parameter is rendered unescaped inside a Vue app root. Unauthenticated attackers can send crafted VueJS template expressions to the /bagisto-common/search endpoint via the 'query' parameter to execute arbitrary JavaScript in victims' browsers.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2024-07-30.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take a deliberate step, such as importing a file or accepting a security prompt.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Webkul Bagisto to 2.2.1 or later (fixed versions per the CVE record).
- The CVE record is tagged "unsupported-when-assigned". The CVE record schema defines it: "Used by the assigning CNA to indicate that when a request for a CVE assignment was received, the product was already end-of-life (EOL) or a product or specific version was deemed not to be supported by the vendor. This tag should only be applied to a CVE Record when all affected products or version lines referenced in the CVE-Record are EOL." (https://github.com/CVEProject/cve-schema/blob/main/schema/tags/cna-tags.json)
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/bagisto-csti.yaml (community template; tests exposure, not compromise).
Affected versions
- 2.1.0 up to, not including, 2.2.1
Fixed versions
- 2.2.1
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 50CVE-2026-126751RetoolRetool versions 3.253.0 before 3.253.19, 3.254.0 before 3.284.12, and 3.285.0 before 3.300.4 contain a DOM-based cross-site scripting vulnerability in the custom-component-collections.html postMessage handler that imports received code without origin validation. Unauthenticated attackers can send crafted postMessage events that load attacker-controlled code via data:text/javascript URIs to execute arbitrary JavaScript in the victim's context.CVSS 5.1EPSS Not scoredReported exploitedCISA due None
What happened
Retool versions 3.253.0 before 3.253.19, 3.254.0 before 3.284.12, and 3.285.0 before 3.300.4 contain a DOM-based cross-site scripting vulnerability in the custom-component-collections.html postMessage handler that imports received code without origin validation. Unauthenticated attackers can send crafted postMessage events that load attacker-controlled code via data:text/javascript URIs to execute arbitrary JavaScript in the victim's context.
Exploitation report
“Exploitation evidence was first observed by the Shadowserver Foundation on 2026-04-22.”
CVE Program, 2026-11-18
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user has to take a deliberate step, such as importing a file or accepting a security prompt.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Retool to the fixed release for your branch: 3.253.19, 3.284.12, 3.300.4 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://docs.retool.com/changelog/disclosures/custom-component-xss
How to check
Exposure check: Nuclei template https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/retool/retool-postmessage-xss.yaml (community template; tests exposure, not compromise).
Affected versions
- 3.253.0 up to, not including, 3.253.19
- 3.254.0 up to, not including, 3.284.12
- 3.285.0 up to, not including, 3.300.4
Fixed versions
- 3.253.19
- 3.284.12
- 3.300.4
Risk record
- Response
- Immediate
- Also rated
- 6.1 Medium under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 51CVE-2026-71499Hefy2027 cf-managercf-manager is an all-in-one dashboard for managing multiple Cloudflare accounts and services. An attacker with deployment API access, or unauthenticated access when API_SECRET is not configured, can make cf-manager access internal resources or fetch attacker-controlled JavaScript and execute it in the victim Cloudflare Workers account.CVSS 10EPSS Not scoredCriticalCISA due None
What happened
cf-manager is an all-in-one dashboard for managing multiple Cloudflare accounts and services. An attacker with deployment API access, or unauthenticated access when API_SECRET is not configured, can make cf-manager access internal resources or fetch attacker-controlled JavaScript and execute it in the victim Cloudflare Workers account.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade hefy2027 cf-manager to 1.1.2 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 1.1.2.
Affected versions
- before 1.1.2
Fixed versions
- 1.1.2
Risk record
- Response
- Immediate
Sources
Number 52CVE-2026-75521Mirendev runtimeMiren Runtime provides the runtime component for the Miren application platform. A network attacker who can reach the listener can present a self-signed certificate with an issuer distinguished name matching the public cluster CA subject and gain cluster superuser access, allowing disclosure, modification, or disruption of applications, sandboxes, disks, credentials, and other managed resources.CVSS 10EPSS Not scoredCriticalCISA due None
What happened
Miren Runtime provides the runtime component for the Miren application platform. A network attacker who can reach the listener can present a self-signed certificate with an issuer distinguished name matching the public cluster CA subject and gain cluster superuser access, allowing disclosure, modification, or disruption of applications, sandboxes, disks, credentials, and other managed resources.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade mirendev runtime to 0.11.1 or later (fixed versions per the CVE record).
- Upgrade the go package miren.dev/runtime to 0.11.1 or later (patched version per GitHub Advisory Database and OSV).
- Statement in the NVD description: This issue is fixed in version 0.11.1.
- Vendor guidance (advisory, not a fix): "Miren recommends that all applications are redeployed and any credentials reference in environment variables are rotated."
If you cannot update yet: Until the patch is deployed, restrict network access to the RPC port (`:8443`) so that it is not reachable from untrusted networks — remove any `0.0.0.0/0` ingress and limit it to trusted management networks. This is a containment measure only and does not remove the underlying vulnerability.
Not a fix: the update is still required.
Affected versions
- before 0.11.1
Fixed versions
- 0.11.1
Risk record
- Response
- Immediate
Sources
Number 53CVE-2026-95787Hewlett Packard Enterprise (HPE) ArubaOS (AOS)Vulnerabilities in the PAPI protocol of AOS-10 could allow an unauthenticated remote attacker to circumvent existing authentication controls.CVSS 10EPSS Not scoredCriticalCISA due None
What happened
Vulnerabilities in the PAPI protocol of AOS-10 could allow an unauthenticated remote attacker to circumvent existing authentication controls.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade to the fixed release for your line (per HPE bulletin hpesbnw05162en_us): "AOS-10.8.x.x: 10.8.1.2 and above", "AOS-10.7.x.x: 10.7.2.7 and above", "AOS-10.4.x.x: 10.4.1.14 and above".
- Follow the vendor advisory: https://support.hpe.com/hpesc/public/api/document/hpesbnw05162en_us
If you cannot update yet: To minimize the likelihood of an attacker exploiting these vulnerabilities, HPE Networking recommends that the CLI and web-based management interfaces be restricted to a dedicated layer 2 segment/VLAN and/or controlled by firewall policies at layer 3 and above along with accounting controls for tracking and logging user activities and resource usage.
Not a fix: the update is still required.
General guidance (MITRE CWE, not a vendor fix)
CWE-269 (Improper Privilege Management). Phase: Architecture and Design, Operation. Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Affected versions
- 10.8.0.0 through 10.8.1.1
- 10.7.0.0 through 10.7.2.6
- 10.4.0.0 through 10.4.1.13
Fixed versions
- 10.8.1.2
- 10.7.2.7
- 10.4.1.14
Risk record
- Response
- Immediate
Sources
Number 54CVE-2026-130778Lxc incusIncus before 7.6.0 contains an authentication bypass vulnerability that allows remote attackers to authenticate as any trusted certificate by appending its public certificate to their presented TLS client chain. Attackers can append the server's or a cluster member's certificate to gain cluster-level access, bypass authorization, modify trust store entries, and influence scriptlet-based authorization decisions.CVSS 10EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 contains an authentication bypass vulnerability that allows remote attackers to authenticate as any trusted certificate by appending its public certificate to their presented TLS client chain. Attackers can append the server's or a cluster member's certificate to gain cluster-level access, bypass authorization, modify trust store entries, and influence scriptlet-based authorization decisions.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-xg75-xf37-cph9
If you cannot update yet: Restrict network access to the HTTPS listener to trusted hosts. There is no configuration based workaround.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 55CVE-2026-129316DokployDokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.13 until 0.31.0, the Docker terminal, container-log, and monitoring WebSocket handlers accept a caller-controlled serviceId as authorization but do not consistently bind the requested containerId or appName to that service. A member with read access to any service can consequently target unrelated containers, obtain a root shell in the Dokploy panel container, read other tenants' logs and statistics, and use the mounted Docker socket to compromise the host.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.13 until 0.31.0, the Docker terminal, container-log, and monitoring WebSocket handlers accept a caller-controlled serviceId as authorization but do not consistently bind the requested containerId or appName to that service. A member with read access to any service can consequently target unrelated containers, obtain a root shell in the Dokploy panel container, read other tenants' logs and statistics, and use the mounted Docker socket to compromise the host.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dokploy to 0.31.0 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 0.31.0.
Affected versions
- 0.29.13 up to, not including, 0.31.0
Fixed versions
- 0.31.0
Risk record
- Response
- Immediate
Sources
Number 56CVE-2026-129986DokployDokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, mount.deleteFileMount passes a path containing the user-controlled filePath to the local removeFileOrDirectory helper, which interpolates it unquoted into rm -rf, while the remote branch is quoted. An authenticated member with file-mount create and delete permissions can execute arbitrary commands in the host context immediately when deleting a local file mount, without requiring a running container.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, mount.deleteFileMount passes a path containing the user-controlled filePath to the local removeFileOrDirectory helper, which interpolates it unquoted into rm -rf, while the remote branch is quoted. An authenticated member with file-mount create and delete permissions can execute arbitrary commands in the host context immediately when deleting a local file mount, without requiring a running container.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dokploy to 0.31.1 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 0.31.1.
Affected versions
- before 0.31.1
Fixed versions
- 0.31.1
Risk record
- Response
- Immediate
Sources
Number 57CVE-2026-129987DokployDokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the database password validation used by the MySQL, PostgreSQL, MariaDB, MongoDB, and Redis change-password procedures permits backticks, and the procedures interpolate attacker-controlled passwords into Bash command strings. An authenticated user who can update a database password can trigger command substitution before the database command runs, resulting in arbitrary operating-system command execution with the Dokploy process privileges, which are typically root.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the database password validation used by the MySQL, PostgreSQL, MariaDB, MongoDB, and Redis change-password procedures permits backticks, and the procedures interpolate attacker-controlled passwords into Bash command strings. An authenticated user who can update a database password can trigger command substitution before the database command runs, resulting in arbitrary operating-system command execution with the Dokploy process privileges, which are typically root.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dokploy to 0.31.1 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 0.31.1.
Affected versions
- before 0.31.1
Fixed versions
- 0.31.1
Risk record
- Response
- Immediate
Sources
Number 58CVE-2026-129989DokployDokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the Nixpacks publishDirectory build setting accepts shell metacharacters and is interpolated into a docker cp command executed through child_process.exec. An authenticated user with access to an application can execute arbitrary commands on the Dokploy host when triggering a Nixpacks deployment, leading to host compromise through the privileged Docker environment.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the Nixpacks publishDirectory build setting accepts shell metacharacters and is interpolated into a docker cp command executed through child_process.exec. An authenticated user with access to an application can execute arbitrary commands on the Dokploy host when triggering a Nixpacks deployment, leading to host compromise through the privileged Docker environment.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dokploy to 0.31.1 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 0.31.1.
Affected versions
- before 0.31.1
Fixed versions
- 0.31.1
Risk record
- Response
- Immediate
Sources
Number 59CVE-2026-129991DokployDokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the backup prefix field is only checked for a nonempty value, and normalizeS3Path preserves shell metacharacters before the prefix is interpolated into rclone upload and retention-cleanup command strings. An authenticated organization member with backup permission for a service can execute arbitrary commands as root on the Dokploy host or configured remote server when a PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose, or web-server backup runs manually, on schedule, or performs retention cleanup.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.31.1, the backup prefix field is only checked for a nonempty value, and normalizeS3Path preserves shell metacharacters before the prefix is interpolated into rclone upload and retention-cleanup command strings. An authenticated organization member with backup permission for a service can execute arbitrary commands as root on the Dokploy host or configured remote server when a PostgreSQL, MySQL, MariaDB, MongoDB, libSQL, Compose, or web-server backup runs manually, on schedule, or performs retention cleanup.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade dokploy to 0.31.1 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 0.31.1.
Affected versions
- before 0.31.1
Fixed versions
- 0.31.1
Risk record
- Response
- Immediate
Sources
Number 60CVE-2026-130759Fleetdm fleetFleet from 4.71.0 before 4.88.2 contains an authentication bypass vulnerability in the SAML SSO callback that looks up sessions using unvalidated client-supplied identifiers. Users able to run live queries or enroll secret holders can plant attacker-controlled identity provider metadata in the session store, then present a self-signed SAML response to log in as a global admin.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Fleet from 4.71.0 before 4.88.2 contains an authentication bypass vulnerability in the SAML SSO callback that looks up sessions using unvalidated client-supplied identifiers. Users able to run live queries or enroll secret holders can plant attacker-controlled identity provider metadata in the session store, then present a self-signed SAML response to log in as a global admin.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade fleetdm fleet (5 products in the CVE record) to the fixed release for your branch: 4.88.2, 4.89.3, 4.90.3, 4.91.2, 4.92.3 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/fleetdm/fleet/security/advisories/GHSA-94f5-6j6w-r3rh
- Vendor guidance (advisory, not a fix): "Fleet instances without SAML SSO are not affected."
- Vendor guidance (advisory, not a fix): "If you run more than one Fleet replica, the issue stays open until every replica is patched. Upgrade all of them."
If you cannot update yet: If you can't upgrade right away, turn off SAML SSO for the Fleet console and end-user MDM flows until all replicas are upgraded.
Not a fix: the update is still required.
Affected versions
- 4.71.0 up to, not including, 4.88.2
- 4.89.0 up to, not including, 4.89.3
- 4.90.0 up to, not including, 4.90.3
- 4.91.0 up to, not including, 4.91.2
- 4.92.0 up to, not including, 4.92.3
Fixed versions
- 4.88.2
- 4.89.3
- 4.90.3
- 4.91.2
- 4.92.3
Risk record
- Response
- Immediate
Sources
Number 61CVE-2026-130771Lxc incusIncus before 7.6.0 fails to reject special files, hard links, or symlinks in backup or image metadata, allowing restricted project users to read or overwrite host files. Attackers can import crafted backups containing device nodes, a hard-linked backup.yaml, or symlinks to corrupt host storage, overwrite host files, or leak other projects' data.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 fails to reject special files, hard links, or symlinks in backup or image metadata, allowing restricted project users to read or overwrite host files. Attackers can import crafted backups containing device nodes, a hard-linked backup.yaml, or symlinks to corrupt host storage, overwrite host files, or leak other projects' data.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-5pgx-q9xx-j3qv
If you cannot update yet: Do not grant image, instance or backup creation to restricted certificates or restricted-project users for untrusted tenants until patched.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 62CVE-2026-130780Lxc incusIncus before 7.6.0 contains a path traversal vulnerability that allows malicious migration peers to write outside intended directories by supplying unvalidated dependent volume and snapshot names in the migration offer header. Attackers controlling a migration source can create root-owned volumes with attacker content at arbitrary host paths, compromising hosts using dir storage pools, bypassing restricted.storage-pools.access, or crashing the daemon.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 contains a path traversal vulnerability that allows malicious migration peers to write outside intended directories by supplying unvalidated dependent volume and snapshot names in the migration offer header. Attackers controlling a migration source can create root-owned volumes with attacker content at arbitrary host paths, compromising hosts using dir storage pools, bypassing restricted.storage-pools.access, or crashing the daemon.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-q9fc-p923-6vp7
If you cannot update yet: Only migrate from trusted servers.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 63CVE-2026-130784Lxc incusIncus before 7.6.0 contains an authorization bypass vulnerability that allows restricted clients to create and access default project resources by exploiting entitlement checks against the requested project. Attackers can create bridge networks with raw.dnsmasq directives to execute code as root on the host, or manipulate inherited resources via the ?project= parameter.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 contains an authorization bypass vulnerability that allows restricted clients to create and access default project resources by exploiting entitlement checks against the requested project. Attackers can create bridge networks with raw.dnsmasq directives to execute code as root on the host, or manipulate inherited resources via the ?project= parameter.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-5c64-j5m6-8433
If you cannot update yet: Setting `restricted.networks.access` on restricted projects to the list of existing networks they may use prevents the creation of networks.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 64CVE-2026-130786Lxc incusIncus before 7.6.0 contains a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in OCI config.json values or oci.entrypoint and oci.cwd keys. Attackers can add liblxc hooks or crafted tmpfs lxc.mount.entry fields to run commands as root on the host or bind-mount host paths, even from restricted projects.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 contains a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in OCI config.json values or oci.entrypoint and oci.cwd keys. Attackers can add liblxc hooks or crafted tmpfs lxc.mount.entry fields to run commands as root on the host or bind-mount host paths, even from restricted projects.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-3wxw-5gh2-j2x2
If you cannot update yet: Only allow trusted image sources.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 65CVE-2026-132139DrayTek Vigor2960A weakness has been identified in DrayTek Vigor2960 up to 1.5.1.6. Executing a manipulation of the argument filename can lead to stack-based buffer overflow. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
A weakness has been identified in DrayTek Vigor2960 up to 1.5.1.6. Executing a manipulation of the argument filename can lead to stack-based buffer overflow. The attack may be performed from remote. The exploit has been made available to the public and could be used for attacks.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade the Vigor2960 firmware to 1.5.1.7 (CVE record: "Upgrading to version 1.5.1.7 is able to address this issue. It is recommended to upgrade the affected component.").
- Patch reference in the CVE record: https://fw.draytek.com.tw/Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip
General guidance (MITRE CWE, not a vendor fix)
CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer). Phase: Operation. Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX.
Affected versions
- 1.5.1.0
- 1.5.1.1
- 1.5.1.2
- 1.5.1.3
- 1.5.1.4
- 1.5.1.5
- 1.5.1.6
Fixed versions
- 1.5.1.7
Risk record
- Response
- Immediate
Sources
Number 66CVE-2026-132141DrayTek Vigor2960A vulnerability was detected in DrayTek Vigor2960 up to 1.5.1.6. The manipulation of the argument usefile results in stack-based buffer overflow. It is possible to launch the attack remotely. The exploit is now public and may be used.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
A vulnerability was detected in DrayTek Vigor2960 up to 1.5.1.6. The manipulation of the argument usefile results in stack-based buffer overflow. It is possible to launch the attack remotely. The exploit is now public and may be used.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade the Vigor2960 firmware to 1.5.1.7 (CVE record: "Upgrading to version 1.5.1.7 can resolve this issue. It is advisable to upgrade the affected component.").
- Patch reference in the CVE record: https://fw.draytek.com.tw/Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip
General guidance (MITRE CWE, not a vendor fix)
CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer). Phase: Operation. Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX.
Affected versions
- 1.5.1.0
- 1.5.1.1
- 1.5.1.2
- 1.5.1.3
- 1.5.1.4
- 1.5.1.5
- 1.5.1.6
Fixed versions
- 1.5.1.7
Risk record
- Response
- Immediate
Sources
Number 67CVE-2026-132143DrayTek Vigor2960A vulnerability has been found in DrayTek Vigor2960 up to 1.5.1.6. This vulnerability affects the function doWebBackup of the file /cgi-bin/mainfunction.cgi of the component Backup Handler. Such manipulation of the argument path/value leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
A vulnerability has been found in DrayTek Vigor2960 up to 1.5.1.6. This vulnerability affects the function doWebBackup of the file /cgi-bin/mainfunction.cgi of the component Backup Handler. Such manipulation of the argument path/value leads to stack-based buffer overflow. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade the Vigor2960 firmware to 1.5.1.7 (CVE record: "Upgrading to version 1.5.1.7 is able to resolve this issue. The affected component should be upgraded.").
- Patch reference in the CVE record: https://fw.draytek.com.tw/Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip
General guidance (MITRE CWE, not a vendor fix)
CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer). Phase: Operation. Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX.
Affected versions
- 1.5.1.0
- 1.5.1.1
- 1.5.1.2
- 1.5.1.3
- 1.5.1.4
- 1.5.1.5
- 1.5.1.6
Fixed versions
- 1.5.1.7
Risk record
- Response
- Immediate
Sources
Number 68CVE-2026-132231JetBrains TeamCityIn JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade JetBrains TeamCity to the fixed release for your branch: 2025.11.7, 2026.1.3 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://www.jetbrains.com/privacy-security/issues-fixed/
Affected versions
- 2026.1 up to, not including, 2026.1.3
- before 2025.11.7
Fixed versions
- 2025.11.7
- 2026.1.3
Risk record
- Response
- Immediate
Sources
Number 69CVE-2026-132232JetBrains TeamCityIn JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade JetBrains TeamCity to the fixed release for your branch: 2025.11.7, 2026.1.3 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://www.jetbrains.com/privacy-security/issues-fixed/
Affected versions
- 2026.1 up to, not including, 2026.1.3
- before 2025.11.7
Fixed versions
- 2025.11.7
- 2026.1.3
Risk record
- Response
- Immediate
Sources
Number 70CVE-2026-132233JetBrains TeamCityIn JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade JetBrains TeamCity to the fixed release for your branch: 2025.11.7, 2026.1.3 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://www.jetbrains.com/privacy-security/issues-fixed/
Affected versions
- 2026.1 up to, not including, 2026.1.3
- before 2025.11.7
Fixed versions
- 2025.11.7
- 2026.1.3
Risk record
- Response
- Immediate
Sources
Number 71CVE-2026-132234JetBrains TeamCityIn JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings.CVSS 9.9EPSS Not scoredCriticalCISA due None
What happened
In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade JetBrains TeamCity to the fixed release for your branch: 2025.11.7, 2026.1.3 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://www.jetbrains.com/privacy-security/issues-fixed/
Affected versions
- 2026.1 up to, not including, 2026.1.3
- before 2025.11.7
Fixed versions
- 2025.11.7
- 2026.1.3
Risk record
- Response
- Immediate
Sources
Number 72CVE-2026-63189N4ze3m dialoqbaseDialoqbase is an application for creating chatbots. Prior to 1.11.5, the unauthenticated GET /api/v1/view/* route in server/src/routes/api/v1/view/root.ts resolves its attacker-controlled wildcard path without normalization or containment, allowing traversal outside the intended uploads directory and arbitrary server file reads. Reading environment files can disclose DB_SECRET_KEY, the application's JWT signing key, which permits forged administrator tokens and takeover of bots, conversations, integrations, and stored third-party credentials.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Dialoqbase is an application for creating chatbots. Prior to 1.11.5, the unauthenticated GET /api/v1/view/* route in server/src/routes/api/v1/view/root.ts resolves its attacker-controlled wildcard path without normalization or containment, allowing traversal outside the intended uploads directory and arbitrary server file reads. Reading environment files can disclose DB_SECRET_KEY, the application's JWT signing key, which permits forged administrator tokens and takeover of bots, conversations, integrations, and stored third-party credentials.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade n4ze3m dialoqbase to 1.11.5 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 1.11.5.
- Vendor guidance (advisory, not a fix): "Operators running `<= 1.11.4` should upgrade to `1.11.5` and rotate `DB_SECRET_KEY`, since it may have been exposed prior to patching."
If you cannot update yet: There is no safe workaround on affected versions other than blocking the route at a reverse proxy.
Not a fix: the update is still required.
Affected versions
- before 1.11.5
Fixed versions
- 1.11.5
Risk record
- Response
- Immediate
Sources
Number 73CVE-2026-73969Ansibleguy76 ansibleformsAnsibleForms is a self-hosted web application that turns automation into self-service forms. An unauthenticated attacker can sign a self-contained token with privileged claims because server/src/auth/auth_jwt.js verifies the signature without reloading the user from the database, and server/src/lib/middleware.js trusts the token's roles and options for authorization. Prior to 6.2.1, AnsibleForms uses a public hard-coded fallback JWT signing secret from server/config/auth.config.js when ACCESS_TOKEN_SECRET is unset. A forged token can therefore be accepted as an administrator session, resulting in authentication bypass and full privileged API access.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
AnsibleForms is a self-hosted web application that turns automation into self-service forms. An unauthenticated attacker can sign a self-contained token with privileged claims because server/src/auth/auth_jwt.js verifies the signature without reloading the user from the database, and server/src/lib/middleware.js trusts the token's roles and options for authorization. Prior to 6.2.1, AnsibleForms uses a public hard-coded fallback JWT signing secret from server/config/auth.config.js when ACCESS_TOKEN_SECRET is unset. A forged token can therefore be accepted as an administrator session, resulting in authentication bypass and full privileged API access.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade ansibleguy76 ansibleforms to 6.2.1 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 6.2.1.
Affected versions
- before 6.2.1
Fixed versions
- 6.2.1
Risk record
- Response
- Immediate
Sources
Number 74CVE-2026-110009unzerplugins Unzer PaymentsThe Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by submitting that user's known email address, receiving valid `wordpress_logged_in_*` session cookies for the targeted account and achieving full site takeover.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
The Unzer Payments plugin for WordPress is vulnerable to Authentication Bypass leading to Account Takeover in all versions up to, and including, 2.2.1. This makes it possible for unauthenticated attackers to log in as any existing WordPress user — including administrators — by submitting that user's known email address, receiving valid `wordpress_logged_in_*` session cookies for the targeted account and achieving full site takeover.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
- WordPress.org plugin page: "This plugin has been closed as of November 11, 2026 and is not available for download. This closure is temporary, pending a full review." https://wordpress.org/plugins/unzer-payments/
General guidance (MITRE CWE, not a vendor fix)
CWE-287 (Improper Authentication). Phase: Architecture and Design. Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Affected versions
- through 2.2.1
Risk record
- Response
- Immediate
Sources
Number 75CVE-2026-110486Eclipse MosquittoIn Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker's user by any client able to establish a session.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker's user by any client able to establish a session.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Eclipse Mosquitto to 2.1.3 (vendor advisory GHSA-6j8m-r32v-4h38: affected versions 2.1.0-2.1.2, patched version 2.1.3).
- Follow the vendor advisory: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/399
If you cannot update yet: For these versions, the risk can be mitigated by disabling websockets support, or by compiling using the libwebsockets implementation.
Not a fix: the update is still required.
General guidance (MITRE CWE, not a vendor fix)
CWE-787 (Out-of-bounds Write). Phase: Operation. Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX.
Affected versions
- 2.1 through 2.1.2
Fixed versions
- 2.1.3
Risk record
- Response
- Immediate
Sources
Number 76CVE-2026-110811trustpayments Trust Payments Gateway for WooCommerce (JavaScript Library)The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.8. This makes it possible for unauthenticated attackers to authenticate as WordPress user ID 1 — the bootstrap site administrator or, on multisite, a network super-admin — by supplying the `new_username` parameter matching any existing login during checkout and visiting the resulting thank-you page. Exploitation requires the Trust Payments gateway to be active and the attacker to complete a paid order on their own account; the ID 1 administrator username is additionally enumerable via standard WordPress user enumeration techniques.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
The Trust Payments Gateway for WooCommerce (JavaScript Library) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.3.8. This makes it possible for unauthenticated attackers to authenticate as WordPress user ID 1 — the bootstrap site administrator or, on multisite, a network super-admin — by supplying the `new_username` parameter matching any existing login during checkout and visiting the resulting thank-you page. Exploitation requires the Trust Payments gateway to be active and the attacker to complete a paid order on their own account; the ID 1 administrator username is additionally enumerable via standard WordPress user enumeration techniques.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
General guidance (MITRE CWE, not a vendor fix)
CWE-287 (Improper Authentication). Phase: Architecture and Design. Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Affected versions
- through 1.3.8
Risk record
- Response
- Immediate
Sources
Number 77CVE-2026-116443Dell PowerStoreDell PowerStore SDNAS contains a stack-based buffer overflow in the NAS TFTP service that could allow an unauthenticated remote attacker to cause a denial of service or potential code execution.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Dell PowerStore SDNAS contains a stack-based buffer overflow in the NAS TFTP service that could allow an unauthenticated remote attacker to cause a denial of service or potential code execution.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Dell PowerStore (15 products in the CVE record) to 5.1.0.0-2798105 or later (fixed versions per the CVE record).
- Dell DSA-2026-479 (4.3.x LTS): Fixes for the vulnerabilities affecting 4.3.x LTS are expected to be released in batches across multiple patches, starting in November 2026.
- Follow the vendor advisory: https://www.dell.com/support/kbdoc/en-us/000527640/dsa-2026-479-dell-powerstore-t-security-update-for-multiple-vulnerabilities
Affected versions
- before 5.1.0.0-2798105
Fixed versions
- 5.1.0.0-2798105
Risk record
- Response
- Immediate
Sources
Number 78CVE-2026-116446Dell PowerStoreDell PowerStore SDNAS contains an out-of-bounds memory vulnerability in the NAS NFS service that an unauthenticated remote attacker could exploit to cause a denial of service.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Dell PowerStore SDNAS contains an out-of-bounds memory vulnerability in the NAS NFS service that an unauthenticated remote attacker could exploit to cause a denial of service.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Dell PowerStore to a fixed release for your line (per the CVE record and Dell DSA-2026-479): PowerStoreT OS 5.1.x to 5.1.0.0-2798105 or later; PowerStoreT OS 4.3.x to 4.3.1.3-2800620 or later.
- Follow the vendor advisory: https://www.dell.com/support/kbdoc/en-us/000527640/dsa-2026-479-dell-powerstore-t-security-update-for-multiple-vulnerabilities
General guidance (MITRE CWE, not a vendor fix)
CWE-787 (Out-of-bounds Write). Phase: Operation. Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX.
Affected versions
- before 4.3.1.3-2800620
- before 5.1.0.0-2798105
Fixed versions
- 5.1.0.0-2798105
- 4.3.1.3-2800620
Risk record
- Response
- Immediate
Sources
Number 79CVE-2026-116448Dell PowerStoreDell PowerStore SDNAS contains an OS Command Injection vulnerability that could allow an attacker with internal network access to execute arbitrary commands as root on the NAS node.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Dell PowerStore SDNAS contains an OS Command Injection vulnerability that could allow an attacker with internal network access to execute arbitrary commands as root on the NAS node.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Dell PowerStore (15 products in the CVE record) to 5.1.0.0-2798105 or later (fixed versions per the CVE record).
Affected versions
- before 5.1.0.0-2798105
Fixed versions
- 5.1.0.0-2798105
Risk record
- Response
- Immediate
Sources
Number 80CVE-2026-116449Dell PowerStoreDell PowerStore SDNAS contains an OS Command Injection vulnerability that could allow an attacker with internal network access to execute arbitrary commands as root on the NAS node.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Dell PowerStore SDNAS contains an OS Command Injection vulnerability that could allow an attacker with internal network access to execute arbitrary commands as root on the NAS node.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Dell PowerStore (15 products in the CVE record) to 5.1.0.0-2798105 or later (fixed versions per the CVE record).
- Dell DSA-2026-479 (4.3.x LTS): Fixes for the vulnerabilities affecting 4.3.x LTS are expected to be released in batches across multiple patches, starting in November 2026.
- Follow the vendor advisory: https://www.dell.com/support/kbdoc/en-us/000527640/dsa-2026-479-dell-powerstore-t-security-update-for-multiple-vulnerabilities
Affected versions
- before 5.1.0.0-2798105
Fixed versions
- 5.1.0.0-2798105
Risk record
- Response
- Immediate
Sources
Number 81CVE-2026-124990Masteriyo LMS – LMS Course Builder, Quizzes & CertificatesThe Masteriyo LMS – LMS Course Builder, Quizzes & Certificates plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 3.5.1 via deserialization of untrusted input in the course importer.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
The Masteriyo LMS – LMS Course Builder, Quizzes & Certificates plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 3.5.1 via deserialization of untrusted input in the course importer.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
- WordPress.org lists 3.5.2 as the current release, newer than the last affected version in the CVE record. A newer release does not prove a fix: confirm it in the plugin changelog.
General guidance (MITRE CWE, not a vendor fix)
CWE-502 (Deserialization of Untrusted Data). Phase: Operation. Use an application firewall that can detect attacks against this weakness.
Affected versions
- through 3.5.1
Risk record
- Response
- Immediate
Sources
Number 82CVE-2026-127021Unknown Flamix: Bitrix24 and WooCommerce Products SyncThe Flamix: Bitrix24 and WooCommerce Products Sync WordPress plugin before 1.7.0 does not restrict or validate an unauthenticated file-exchange request, allowing anyone to write a file with an attacker-chosen name, extension and path to a web-served location and thereby execute arbitrary PHP.CVSS 9.8EPSS Not scoredCriticalCISA due None
NVD description
The Flamix: Bitrix24 and WooCommerce Products Sync WordPress plugin before 1.7.0 does not restrict or validate an unauthenticated file-exchange request, allowing anyone to write a file with an attacker-chosen name, extension and path to a web-served location and thereby execute arbitrary PHP.
Products
Unknown Flamix: Bitrix24 and WooCommerce Products Sync (CVE.org CNA)
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Unknown Flamix: Bitrix24 and WooCommerce Products Sync: Fixed in 1.7.0 (per CVE.org CNA)
Advisories and references from the CNA
Supplied by the CVE Numbering Authority (CNA); publishers vary.
Affected versions
- Unknown Flamix: Bitrix24 and WooCommerce Products Sync: before 1.7.0 (semver) (CVE.org CNA)
A range's end is the first version the record places outside that range; it does not say later versions or other release lines are unaffected. Check the vendor advisory.
Versions the record lists as not affected
Not listed yet
CISA SSVC assessment
Not listed yet
Risk record
- NVD status
- Received
- Severity
- Critical
- CVSS
- 9.8 (v3.1)
- EPSS
- Not listed yet
- Published
- Nov 18, 2026
- Weakness
- CWE-434
Sources
Number 83CVE-2026-128851Unknown Probono Form BasicThe Probono Form Basic WordPress plugin before 1.3.3 does not validate the real type of files uploaded through its public form, trusting the client-declared MIME type instead, which could allow unauthenticated attackers to upload PHP files to a public directory and execute them before they are…CVSS 9.8EPSS Not scoredCriticalCISA due None
NVD description
The Probono Form Basic WordPress plugin before 1.3.3 does not validate the real type of files uploaded through its public form, trusting the client-declared MIME type instead, which could allow unauthenticated attackers to upload PHP files to a public directory and execute them before they are…
Products
Unknown Probono Form Basic (CVE.org CNA)
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Unknown Probono Form Basic: Fixed in 1.3.3 (per CVE.org CNA)
Advisories and references from the CNA
Supplied by the CVE Numbering Authority (CNA); publishers vary.
Affected versions
- Unknown Probono Form Basic: before 1.3.3 (semver) (CVE.org CNA)
A range's end is the first version the record places outside that range; it does not say later versions or other release lines are unaffected. Check the vendor advisory.
Versions the record lists as not affected
Not listed yet
CISA SSVC assessment
Not listed yet
Risk record
- NVD status
- Received
- Severity
- Critical
- CVSS
- 9.8 (v3.1)
- EPSS
- Not listed yet
- Published
- Nov 18, 2026
- Weakness
- CWE-434
Sources
Number 84CVE-2026-130675Craftcms cmsCraft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform() that allows attackers to instantiate arbitrary classes by supplying class:null with a __class key. Attackers can reach the method through Craft Commerce's payments/pay redirect template calling customer.photo.getUrl() with a crafted transform to instantiate classes like yii\rbac\PhpManager and execute PHP.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Craft CMS from 5.0.0 before 5.11.4 contains a remote code execution vulnerability in ImageTransforms::normalizeTransform() that allows attackers to instantiate arbitrary classes by supplying class:null with a __class key. Attackers can reach the method through Craft Commerce's payments/pay redirect template calling customer.photo.getUrl() with a crafted transform to instantiate classes like yii\rbac\PhpManager and execute PHP.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade craftcms cms to 5.11.4 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/craftcms/cms/security/advisories/GHSA-hq78-cm2m-h24h
Affected versions
- 5.0.0 up to, not including, 5.11.4
Fixed versions
- 5.11.4
Risk record
- Response
- Immediate
Sources
Number 85CVE-2026-130733Getgrav gravGrav from 2.0.0 before 2.2.18 contains an authorization bypass vulnerability that allows publishers to overwrite pages their per-page permissions deny by abusing FolderStorage key delimiter collisions and PageStorage folder reconstruction. Attackers can rename a folder like locked*** or save from a page with an unusual prefix width through a front-end Flex pages form, replacing protected content and permissions to access the protected subtree.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Grav from 2.0.0 before 2.2.18 contains an authorization bypass vulnerability that allows publishers to overwrite pages their per-page permissions deny by abusing FolderStorage key delimiter collisions and PageStorage folder reconstruction. Attackers can rename a folder like locked*** or save from a page with an unusual prefix width through a front-end Flex pages form, replacing protected content and permissions to access the protected subtree.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade getgrav grav to 2.2.18 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/getgrav/grav/security/advisories/GHSA-3rxf-jpgc-hwpv
Affected versions
- 2.0.0 up to, not including, 2.2.18
Fixed versions
- 2.2.18
Risk record
- Response
- Immediate
Sources
Number 86CVE-2026-130754LaradashboardAll versions of LaraDashboard contain an authentication bypass in SocialAuthService::findOrCreateUser(), which links a social login to an existing account by email without checking that the OAuth provider verified that email. Unauthenticated attackers using an OAuth/OIDC provider that asserts a victim's email can log in as any user, including Superadmin, and keep persistent access through a linked social_accounts entry.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
All versions of LaraDashboard contain an authentication bypass in SocialAuthService::findOrCreateUser(), which links a social login to an existing account by email without checking that the OAuth provider verified that email. Unauthenticated attackers using an OAuth/OIDC provider that asserts a victim's email can log in as any user, including Superadmin, and keep persistent access through a linked social_accounts entry.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- No fixed version or vendor solution for this product is confirmed in the CVE or NVD records. Check the vendor advisory for the current patch status.
- Follow the vendor advisory: https://github.com/laradashboard/laradashboard/security/advisories/GHSA-c5x3-wvxj-7cgr
General guidance (MITRE CWE, not a vendor fix)
CWE-287 (Improper Authentication). Phase: Architecture and Design. Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Affected versions
- through 1.5.4
Risk record
- Response
- Immediate
Sources
Number 87CVE-2026-130756Pnpm exeNetwork attackers holding a recovered intermediate key can intercept standalone pnpm registry fetches and serve forged package metadata or tarballs.CVSS 9.8EPSS Not scoredCriticalCISA due None
What happened
Network attackers holding a recovered intermediate key can intercept standalone pnpm registry fetches and serve forged package metadata or tarballs.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade pnpm exe (2 products in the CVE record) to the fixed release for your branch: 10.34.8, 11.28.8 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/pnpm/pnpm/security/advisories/GHSA-w8f5-6m3h-r453
Affected versions
- before 10.34.8
- 11.0.0 up to, not including, 11.28.8
Fixed versions
- 10.34.8
- 11.28.8
Risk record
- Response
- Immediate
Sources
Number 88CVE-2026-55506WavelogWavelog is web-based amateur radio logging software. A standard authenticated user can associate the malicious filename with the user's own QSO, satisfy the ownership check, escape the per-user QSL image directory, and delete files writable by the PHP worker.CVSS 9.6EPSS Not scoredCriticalCISA due None
What happened
Wavelog is web-based amateur radio logging software. A standard authenticated user can associate the malicious filename with the user's own QSO, satisfy the ownership check, escape the per-user QSL image directory, and delete files writable by the PHP worker.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade wavelog to 2.5 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 2.5.
If you cannot update yet: If upgrading is not immediately possible, restrict account creation to trusted operators and audit existing user accounts. Operators can additionally remove write permissions on the `install/` directory at the filesystem level once installation is complete, which breaks the installer-replay portion of the chain even if the deletion primitive itself remains reachable. In Docker Setups an admin can mount an empty directory to /install.
Not a fix: the update is still required.
Affected versions
- before 2.5
Fixed versions
- 2.5
Risk record
- Response
- Immediate
Sources
Number 89CVE-2026-130779Lxc incusIncus before 7.6.0 contains a path traversal vulnerability that allows users permitted to import custom volumes to store unvalidated snapshot names from the backup index configuration section. Attackers can craft a backup with traversal sequences in snapshot names so later deletion removes arbitrary host directories as root, while renaming or mounting operates on arbitrary paths.CVSS 9.6EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 contains a path traversal vulnerability that allows users permitted to import custom volumes to store unvalidated snapshot names from the backup index configuration section. Attackers can craft a backup with traversal sequences in snapshot names so later deletion removes arbitrary host directories as root, while renaming or mounting operates on arbitrary paths.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-p45f-gqqj-6qq3
If you cannot update yet: Only allow trusted users to import custom volumes.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 90CVE-2026-130783Lxc incusIncus before 7.6.0 exposes certificate and cluster join token secrets through the default project event stream and skips authorization when cancelling operations without associated permissions.CVSS 9.6EPSS Not scoredCriticalCISA due None
What happened
Incus before 7.6.0 exposes certificate and cluster join token secrets through the default project event stream and skips authorization when cancelling operations without associated permissions.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade lxc incus to 7.6.0 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/lxc/incus/security/advisories/GHSA-cwg9-8mc4-hf7j
If you cannot update yet: Only issue restricted certificates for projects other than the default project, as operation events are only delivered to clients allowed to view events in the operation's project.
Not a fix: the update is still required.
Affected versions
- before 7.6.0
Fixed versions
- 7.6.0
Risk record
- Response
- Immediate
Sources
Number 91CVE-2026-116441Dell PowerStoreDell PowerStore SDNAS contains an out-of-bounds write vulnerability in the storage-processor interconnect driver that could allow a malicious peer to execute code with system privileges.CVSS 9.6EPSS Not scoredCriticalCISA due None
What happened
Dell PowerStore SDNAS contains an out-of-bounds write vulnerability in the storage-processor interconnect driver that could allow a malicious peer to execute code with system privileges.
Who can attack it
Someone on a nearby or limited network, such as the same subnet, Wi-Fi or Bluetooth range, or a secured network zone reached by VPN. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade Dell PowerStore (15 products in the CVE record) to 5.1.0.0-2798105 or later (fixed versions per the CVE record).
- Dell DSA-2026-479 (4.3.x LTS): Fixes for the vulnerabilities affecting 4.3.x LTS are expected to be released in batches across multiple patches, starting in November 2026.
- Follow the vendor advisory: https://www.dell.com/support/kbdoc/en-us/000527640/dsa-2026-479-dell-powerstore-t-security-update-for-multiple-vulnerabilities
Affected versions
- before 5.1.0.0-2798105
Fixed versions
- 5.1.0.0-2798105
Risk record
- Response
- Immediate
Sources
Number 92CVE-2026-19707Product not listed yetA bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed…CVSS 9.5EPSS Not scoredCriticalCISA due None
NVD description
A bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed…
Products
Not listed yet
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link. The attacker also has to get around security protections in place on the system. It also depends on specific conditions of how the system is deployed or running, such as a race the attacker must win or a place on the network path.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
The record does not name a fixed version. Check the vendor advisory.
Advisories and references from the CNA
Not listed yet
Affected versions
Not listed yet
Versions the record lists as not affected
Not listed yet
CISA SSVC assessment
Not listed yet
Risk record
- NVD status
- Received
- Severity
- Critical
- CVSS
- 9.5 (v4.0)
- EPSS
- Not listed yet
- Published
- Nov 18, 2026
- Weakness
- CWE-122
Sources
Number 93CVE-2026-129961LMSLMS (Lan Management System) is vulnerable to Remote Code Execution in its e-mail-based Helpdesk ticket intake. A remote unauthenticated attacker can e-mail a Helpdesk ticket with such an attachment; in the default configuration, anyone can request the uploaded file's URL which executes attacker-supplied code with the privileges of the web server process.CVSS 9.5EPSS Not scoredCriticalCISA due None
What happened
LMS (Lan Management System) is vulnerable to Remote Code Execution in its e-mail-based Helpdesk ticket intake. A remote unauthenticated attacker can e-mail a Helpdesk ticket with such an attachment; in the default configuration, anyone can request the uploaded file's URL which executes attacker-supplied code with the privileges of the web server process.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link. It also depends on specific conditions of how the system is deployed or running, such as a race the attacker must win or a place on the network path.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Fixed by commit d5059b1 (patch commit in the CVE record; the records do not name its branch): https://github.com/chilek/lms/commit/d5059b1ee9e0cf8277a8e8a3be09740f31110205
Risk record
- Response
- Immediate
Sources
Number 94CVE-2026-55508WavelogWavelog is web-based amateur radio logging software. An unauthenticated remote attacker can use UNION-based SQL injection to read arbitrary application database records, including account data, password hashes, API keys, station credentials, reset tokens, QSO data, and station metadata.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
Wavelog is web-based amateur radio logging software. An unauthenticated remote attacker can use UNION-based SQL injection to read arbitrary application database records, including account data, password hashes, API keys, station credentials, reset tokens, QSO data, and station metadata.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade wavelog to 2.5 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 2.5.
If you cannot update yet: If upgrading is not immediately possible, block external access to the `/oqrs/search_log` endpoint at the reverse proxy or web server layer until the patched version can be deployed.
Not a fix: the update is still required.
Affected versions
- before 2.5
Fixed versions
- 2.5
Risk record
- Response
- Immediate
Sources
Number 95CVE-2026-130156Morpheus65535 bazarrBazarr is a companion application to Sonarr and Radarr. Prior to 1.6.3-beta.11, the /api/subtitles/subtitles-info handler uses SubtitleNameContents.get() in subtitles_contents.py and reads the caller-supplied subtitlePath after checking only its subtitle extension; because the resolved path is not confined to files indexed by Bazarr, traversal can read files outside the media library.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
Bazarr is a companion application to Sonarr and Radarr. Prior to 1.6.3-beta.11, the /api/subtitles/subtitles-info handler uses SubtitleNameContents.get() in subtitles_contents.py and reads the caller-supplied subtitlePath after checking only its subtitle extension; because the resolved path is not confined to files indexed by Bazarr, traversal can read files outside the media library.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade morpheus65535 bazarr to 1.6.3-beta.11 or later (fixed versions per the CVE record).
- Statement in the NVD description: This issue is fixed in version 1.6.3-beta.11.
Affected versions
- before 1.6.3-beta.11
Fixed versions
- 1.6.3-beta.11
Risk record
- Response
- Immediate
Sources
Number 96CVE-2026-130680Siyuan-note siyuanSiYuan from 3.3.0 before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to inject HTML via unescaped checkbox column names in Gallery and Kanban AttributeView renderers. Attackers can share a crafted .sy.zip document whose rendering in the Electron desktop client with nodeIntegration enabled executes Node.js and host OS commands.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
SiYuan from 3.3.0 before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to inject HTML via unescaped checkbox column names in Gallery and Kanban AttributeView renderers. Attackers can share a crafted .sy.zip document whose rendering in the Electron desktop client with nodeIntegration enabled executes Node.js and host OS commands.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user only has to take an ordinary step, such as viewing an altered web page.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade siyuan-note siyuan to 3.8.10 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-g275-mf26-qx9r
Affected versions
- 3.3.0 up to, not including, 3.8.10
Fixed versions
- 3.8.10
Risk record
- Response
- Immediate
- Also rated
- 9.6 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 97CVE-2026-130682Siyuan-note siyuanSiYuan before 3.8.10 persists a table block's caption attribute into IAL properties without HTML sanitization, causing stored cross-site scripting upon import or sync. Attackers can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context to achieve remote code execution.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
SiYuan before 3.8.10 persists a table block's caption attribute into IAL properties without HTML sanitization, causing stored cross-site scripting upon import or sync. Attackers can inject an entity-encoded caption with an onerror handler that executes in the Electron client's nodeIntegration context to achieve remote code execution.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need no account or rights on the affected product, and a user only has to take an ordinary step, such as viewing an altered web page.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade siyuan-note siyuan to 3.8.10 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-v92g-4rrc-c6wv
Affected versions
- before 3.8.10
Fixed versions
- 3.8.10
Risk record
- Response
- Immediate
- Also rated
- 9.6 Critical under CVSS 3.1, by disclosure@vulncheck.com
Sources
Number 98CVE-2026-127143LMSAn attacker with access to the web server process or with write access to the LMS database can register a malicious library and trigger a configuration reload, causing lmsd to load and execute it. LMS (Lan Management System) is vulnerable to privilege escalation in the lmsd daemon. Because the example systemd unit does not set a separate user, lmsd runs as root, allowing the attacker to execute arbitrary code with root privileges.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
An attacker with access to the web server process or with write access to the LMS database can register a malicious library and trigger a configuration reload, causing lmsd to load and execute it. LMS (Lan Management System) is vulnerable to privilege escalation in the lmsd daemon. Because the example systemd unit does not set a separate user, lmsd runs as root, allowing the attacker to execute arbitrary code with root privileges.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and no one else has to do anything, such as open a file or click a link.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Fixed by commit 89dd3f7 (patch commit in the CVE record; the records do not name its branch): https://github.com/chilek/lms/commit/89dd3f75168a99f1a0a3539957d08715bb86ab4f
- Vendor guidance (advisory, not a fix): "This issue was fixed in commit 89dd3f7. The lmsd component was removed. For existing installations that use lmsd, the recommended solution is to disable and remove this component."
Risk record
- Response
- Immediate
Sources
Number 99CVE-2026-130678Siyuan-note siyuanSiYuan before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to execute script by storing malicious Attribute View column names rendered unescaped in col.ts. Attackers can inject HTML via addAttributeViewKey, .sy.zip import, or sync, and when a victim adds or duplicates the column, insertAdjacentHTML runs JavaScript with Node.js privileges for desktop code execution.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability that allows attackers to execute script by storing malicious Attribute View column names rendered unescaped in col.ts. Attackers can inject HTML via addAttributeViewKey, .sy.zip import, or sync, and when a victim adds or duplicates the column, insertAdjacentHTML runs JavaScript with Node.js privileges for desktop code execution.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and a user only has to take an ordinary step, such as viewing an altered web page.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade siyuan-note siyuan to 3.8.10 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-vvqj-4crq-p53p
Affected versions
- before 3.8.10
Fixed versions
- 3.8.10
Risk record
- Response
- Immediate
Sources
Number 100CVE-2026-130681Siyuan-note siyuanSiYuan before 3.8.10 contains a stored cross-site scripting vulnerability, an incomplete fix for CVE-2026-44670, because renderAVAttribute() inserts an Attribute View name unescaped into the database row attribute panel header. Attackers who can persist the name, such as via the setAttrViewName action, can inject an onerror handler that runs OS commands through Node.js when a desktop user opens the panel.CVSS 9.4EPSS Not scoredCriticalCISA due None
What happened
SiYuan before 3.8.10 contains a stored cross-site scripting vulnerability, an incomplete fix for CVE-2026-44670, because renderAVAttribute() inserts an Attribute View name unescaped into the database row attribute panel header. Attackers who can persist the name, such as via the setAttrViewName action, can inject an onerror handler that runs OS commands through Node.js when a desktop user opens the panel.
Who can attack it
Someone who can reach it over a network, up to and including the internet. They need basic user rights on the affected product, and a user only has to take an ordinary step, such as viewing an altered web page.
From the CVSS vector in the NVD record, scored by an organization other than NIST.
How to fix
- Upgrade siyuan-note siyuan to 3.8.10 or later (fixed versions per the CVE record).
- Follow the vendor advisory: https://github.com/siyuan-note/siyuan/security/advisories/GHSA-7gj8-xf7w-hfjf
Affected versions
- before 3.8.10
Fixed versions
- 3.8.10
Risk record
- Response
- Immediate
Sources
Sources
The brief now draws on 42 sources: 12 vulnerability data sources, 3 detection rule sets, 4 authorities, 8 press outlets and 15 research teams and blogs. This issue cites 40 publishers, listed below; each row lists its own links. We keep adding reliable, accurate sources as we go, so the brief helps organizations and society act in time. Sources checked November 19, 2026 at 12:00 a.m. EST.
- Authorities
- CVE Program135
- NVD API135
- GitHub Advisory Database80
- OSV59
- CISA KEV5
- Canadian Centre for Cyber Security2
- CERT Polska1
- WordPress.org Plugin Directory1
- Vendors
- Apple15
- F512
- lxc8
- nginx.org5
- siyuan-note5
- Dell4
- JetBrains4
- Eclipse Foundation3
- getgrav3
- nocodb3
- craftcms2
- fleetdm2
- Synology2
- wavelog2
- WWBN2
- Apache1
- ArangoDB1
- chamilo1
- dagu-org1
- Hewlett Packard Enterprise (HPE)1
- laradashboard1
- n4ze3m1
- pnpm1
- Retool1
- SIR (gnuboard)1
- WordPress.org1
- Research teams
- Google Cloud Blog1
- Mandiant1
- Press
- BleepingComputer1
- Rapid71
- The Hacker News1
- The Record1
Coverage is limited to the entries shown. Canadian context requires cited Canadian evidence; worldwide incident and campaign collection is still being expanded. The JSON Feed includes the matching data and original verification timestamps.