Plcwinnt vulnerabilitiesRanked by how likely they are to be used.

Product4 versions
The short answer

Plcwinnt is made by Codesys. We track 17 published vulnerabilities in it, across 4 versions. None of them is on the list of flaws known to be exploited today. If you run Plcwinnt, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Plcwinnt vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Plcwinnt's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Plcwinnt flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 7.4%

    CODESYS V2 runtime system SP before 2.4.7.55 has a Heap-based Buffer Overflow.

    CVSS7.5Published25 May 2021
  2. 7.2%

    CODESYS V2 runtime system before 2.4.7.55 has Improper Input Validation.

    CVSS7.5Published25 May 2021
  3. 2.7%

    In CODESYS V2 Runtime Toolkit 32 Bit full and PLCWinNT prior to versions V2.4.7.56 unauthenticated crafted invalid requests may result in several denial-of-service conditions.

    CVSS7.5Published26 Oct 2021
  4. 1.4%

    In multiple CODESYS products, a low privileged remote attacker may craft a request, which may cause a heap-based buffer overflow, resulting in a denial-of-service condition or memory overwrite.

    CVSS8.8Published24 Jun 2022
  5. 1.2%

    3S-Smart CODESYS SP Realtime NT before V2.3.7.28, CODESYS Runtime Toolkit 32 bit full before V2.4.7.54, and CODESYS PLCWinNT before V2.4.7.54 allow a NULL pointer dereference.

    CVSS6.5Published20 Dec 2019
  6. 1.2%

    In CODESYS V2 PLCWinNT and Runtime Toolkit 32 in versions prior to V2.4.7.57 password protection is not enabled by default and there is no information or prompt to enable password protection at login in case no...

    CVSS9.8Published24 Jun 2022
  7. 1.2%

    In multiple CODESYS products, file download and upload function allows access to internal files in the working directory e.g.

    CVSS8.8Published24 Jun 2022
  8. 1.2%

    In multiple CODESYS products, a remote attacker may craft a request which may cause an unexpected sign extension, resulting in a denial-of-service condition or memory overwrite.

    CVSS8.8Published24 Jun 2022
  9. 1.1%

    Multiple CODESYS Products are prone to a out-of bounds read or write access.

    CVSS8.1Published24 Jun 2022
  10. 1.1%

    Multiple products of CODESYS implement a improper error handling.

    CVSS8.1Published24 Jun 2022
Precursor Intelligence

Running Plcwinnt? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 17 published vulnerabilities listed under the name Plcwinnt, across 4 versions.

None of Plcwinnt's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Plcwinnt. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.