Secuno
ENNL
Book demo

CVE-2026-88795

9.0 CRITICAL
  1. Published17 Sept 2026

Description

The wpShopGermany IT-RECHT KANZLEI WordPress plugin before 2.4 does not generate its API authentication token securely, deriving it from data the requester controls and creating it as a side effect of the check that is supposed to validate it, allowing unauthenticated attackers to predict the token and use the access it grants to write arbitrary files, leading to remote code execution.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-9293710.0
vm2 3.11.6 is vulnerable to a sandbox escape leading to remote code execution in the…
CVE-2026-6210410.0
Unauthenticated Remote Code Execution (RCE) in Migratico Lite <= 2.6.8…
CVE-2026-925938.8
Craft CMS versions 5.10.0 through 5.10.12 contain an incomplete fix for CVE-2026-55794:…
CVE-2026-7345610.0
Under certain circumstances on affected platforms running Arista EOS with gRPC Network…
CVE-2026-921278.0
Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier automatically approves…
CVE-2026-921258.8
Jenkins Script Security Plugin 1415.v9a_f9b_3a_c253d and earlier does not reject the…

Frequently asked

Is CVE-2026-88795 being actively exploited?

CVE-2026-88795 is not in the CISA KEV catalog.

How severe is CVE-2026-88795?

CVE-2026-88795 has a CVSS 3.1 base score of 9.0, rated critical.

How do I fix CVE-2026-88795?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-88795 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.