How severe is CVE-2026-28185?

CVE-2026-28185 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-28185 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-28185?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-28185 published?

CVE-2026-28185 was published on 2026-08-13 and last updated on 2026-08-14.

CVE-2026-28185

CVE-2026-28185 is a critical-severity vulnerability with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-345.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-345
Published: 2026-08-13
Last modified: 2026-08-14

Description

Unauthenticated Broken Authentication in Log in with Google <= 1.4.2 versions.

Frequently asked questions

What is CVE-2026-28185?: Unauthenticated Broken Authentication in Log in with Google <= 1.4.2 versions.
How severe is CVE-2026-28185?: CVE-2026-28185 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-28185 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-28185?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-28185 published?: CVE-2026-28185 was published on 2026-08-13 and last updated on 2026-08-14.

References

https://patchstack.com/database/wordpress/plugin/login-with-google/vulnerability/wordpress-log-in-with-google-plugin-1-4-2-broken-authentication-vulnerability?_s_id=cve

Other CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities

CVE-2026-35051 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an…
CVE-2014-8165 — Critical (CVSS 10.0): scripts/amsvis/powerpcAMS/amsnet.py in powerpc-utils-python uses the pickle Python module unsafely, which allows remote…
CVE-2026-50195 — Critical (CVSS 9.9): containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a vulnerability in the…
CVE-2022-36130 — Critical (CVSS 9.9): HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated…
CVE-2026-74875 — Critical (CVSS 9.8): openssl_encrypt versions before 1.4.0 silently skip JSON schema validation when the jsonschema library is not…
CVE-2026-50214 — Critical (CVSS 9.8): The /v1/Plan service relies entirely on a shared global API token for full administrative management, allowing…

Browse all CWE-345 (Insufficient Verification of Data Authenticity) vulnerabilities →