LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47818: WordPress LWS Hide Login plugin <= 2.1.8 - Secret Login Page Location Disclosure on Multisites vulnerability

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in LWS LWS Hide Login allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects LWS Hide Login: from n/a through 2.1.8.

LowCVSS 3.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This issue can expose the hidden login page location for WordPress multisite installations using LWS Hide Login through version 2.1.8. It does not grant account access by itself, but it weakens a concealment control intended to reduce login page discovery.

Executive priority

Treat this as a low-severity hygiene issue, not an emergency. Prioritize it where WordPress multisite supports sensitive business operations or where hidden login URLs are treated as a primary protection layer.

Technical view

CVE-2023-47818 is a CWE-200 sensitive information exposure in the LWS Hide Login WordPress plugin. The reported impact is disclosure of the secret login page location on multisite deployments. CVSS 3.1 is 3.7 with network access, no privileges, no user interaction, high attack complexity, and low confidentiality impact.

Likely exposure

Exposure is most relevant to WordPress multisite environments running LWS Hide Login through 2.1.8. Single-site installations are not identified in the provided description. The source bundle does not provide CPEs or deployment telemetry, so exposure should be confirmed by plugin inventory.

Exploitation context

The bundle does not report active exploitation, and KEV status is false. The practical risk is reconnaissance: an unauthenticated actor may learn a hidden login URL, increasing pressure on normal login security controls such as passwords, MFA, rate limits, and monitoring.

Researcher notes

The available evidence identifies information disclosure only, with no integrity or availability impact. Patch or workaround details are not included in the source bundle beyond the affected range through 2.1.8. Avoid assuming broader product impact without vendor confirmation.

Mitigation direction

  • Inventory WordPress multisite sites using LWS Hide Login.
  • Check installed plugin versions and flag versions through 2.1.8.
  • Review LWS or Patchstack guidance for fixed releases or workarounds.
  • Ensure login security does not rely on URL hiding alone.
  • Apply MFA, rate limiting, and monitoring for WordPress authentication where available.

Validation and detection

  • Confirm whether each WordPress deployment is multisite.
  • Confirm whether LWS Hide Login is installed and enabled.
  • Record plugin version and compare it with the affected range.
  • Review access logs for unusual requests to hidden login locations.
  • Document compensating controls protecting WordPress authentication.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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 lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47818 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2023-47818Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LWSLWS Hide Loginlws-hide-login, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.