winter-ingenieure.de

The Cyber Exposure Score is a published 0–100 formula built only from publicly observable signals. How this is calculated.

This domain scores better than 65% of the 456 Manufacturing organisations we track (cohort median 78). The sample is seeded from public incident data, not a random cross-section of the sector.

Posture summary

Software versions inside a published affected range (1, 1 known-exploited)

The public response carried a version for these products, and NVD publishes an affected range that contains it. This is not proof the software is unpatched — a distribution backport keeps the original version string while carrying the fix, so a fully patched build can appear here. Both halves of the comparison are public and checkable.

Ransomware leak-site listings (1)

This domain is named on the public leak site of a ransomware group. A leak-site post is a claim published by the group — not a verified fact, and not a statement by this organization. Groups list victims who did not pay, overstate what they hold, and occasionally name the wrong company. What is certain is that the listing itself is public.

Leak-site postings are collected here from 2026-07-30 onwards; an earlier listing would not appear above.

Source: Ransomware.live

Public attack surface (16 hostnames in Certificate Transparency)

Hostnames this organization published in public TLS certificates. Passive OSINT — nothing was scanned.

From the names alone: 2 remote access or sign-in, 0 admin tools, 1 non-production.

The hostname inventory — which forgotten hosts exist and where — is part of the complete audit for this domain.

Hosting footprint (13 of 16 known hostnames resolve)

Where this organisation's hostnames seen in Certificate Transparency actually point. A concentration in one provider is a resilience consideration, not a fault.

Recommendations

• mediumEnable DNSSEC

  DNSSEC signing was not detected for this domain.

• criticalPatch known-exploited vulnerabilities

  1 known-exploited vulnerability(ies) may affect exposed services. Prioritize patching.

• criticalPatch what already has a public exploit

  1 vulnerability(ies) reported on this host have working exploit code published (Exploit-DB, Metasploit, Nuclei or a public PoC). Exploitation needs no development effort — patch these first.

• criticalConfirm software versions that fall inside a published affected range

  The public response carried a version for 1 detected product(s), and 1 published CVE range contains what we read. WordPress 7.0.2 falls inside the range published as affected by CVE-2026-87902 (>= 7.0 and < 7.0.6). 1 is on CISA's known-exploited list, meaning exploitation has been observed in the wild. This is an observation about a version string, not proof the software is unpatched: a distribution backport keeps the original version while carrying the fix. Check the build you are actually running, and patch or upgrade whatever is genuinely inside the range.

• criticalTreat data published on a leak site as disclosed

  This domain is named on akira's public leak site on 2026-08-25. A leak-site post is a claim published by the group, not a verified fact — but the post itself is public, and if it is accurate the data is already out. Confirm the claim, then work from the assumption of disclosure: rotate every credential that touched the affected systems, invalidate active sessions, and check your notification duties under GDPR Art. 33/34.