Security readout for executives and security teams
Plain-English summary
WordPress sites using rtCamp’s Log in with Google plugin through version 1.4.2 may allow an unauthenticated remote attacker to bypass authentication. The supplied CVSS rating indicates potential complete compromise of confidentiality, integrity, and availability, but the sources provided do not describe the precise impact or attack method.
Executive priority
Treat this as an urgent exposure-assessment and remediation task for public WordPress systems. The critical score and unauthenticated attack profile justify rapid action, while the absence of confirmed exploitation and incomplete fix details require validation through authoritative guidance.
Technical view
CVE-2026-28185 is classified as broken authentication associated with CWE-345, indicating inadequate verification of authenticity. Its CVSS 3.1 vector describes a network-accessible, low-complexity issue requiring neither privileges nor user interaction. The supplied evidence does not identify affected configurations, technical root cause, patched version, or vendor-approved remediation.
Likely exposure
Prioritize internet-accessible WordPress installations running Log in with Google version 1.4.2 or earlier. Exposure depends on whether the vulnerable plugin and authentication functionality are present. The bundle’s structured affected-version field is incomplete, so confirm applicability against current vendor or Patchstack guidance.
Exploitation context
The CVE is not listed in the supplied KEV data, and no cited evidence states that active exploitation or public exploit code exists. This does not prove exploitation is absent. Its unauthenticated, remote, low-complexity CVSS characteristics make exposed systems potentially attractive targets.
Researcher notes
The source bundle provides severity, vector, CWE, plugin identity, and the affected ceiling from the title and description. It does not provide root-cause details, exploit prerequisites beyond CVSS, affected configuration nuances, indicators of compromise, or a fixed version. Avoid stronger conclusions until the linked records provide those details.
Mitigation direction
- Inventory WordPress sites for the Log in with Google plugin and record exact versions.
- Check current vendor or Patchstack guidance for a fixed release or approved mitigation.
- Disable the affected plugin where operationally feasible until authoritative remediation is confirmed.
- Review privileged WordPress accounts and revoke suspicious sessions or access.
Validation and detection
- Confirm whether each site runs Log in with Google version 1.4.2 or earlier.
- Determine whether the plugin’s login functionality is exposed to untrusted networks.
- Review authentication and account records for unexpected logins, accounts, or privilege changes.
- After remediation, verify the vulnerable version is absent and intended authentication still works.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-345: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-28185 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/wordpress/plugin/login-with-google/vulnerability/wordpress-log-in-with-google-plugin-1-4-2-broken-authentication-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.