LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45084: WordPress Loginizer Plugin <= 1.7.5 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Softaculous Loginizer plugin <= 1.7.5 versions.

HighCVSS 7.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-45084 affects the WordPress Loginizer plugin at versions 1.7.5 and earlier. It is an unauthenticated reflected cross-site scripting issue. An attacker could trick a user into interacting with a malicious link, potentially affecting browser-side confidentiality, integrity, and availability on a vulnerable site.

Executive priority

Prioritize remediation for internet-facing WordPress properties because the issue is unauthenticated and high severity. It is below emergency KEV-level urgency based on the provided evidence, but should not wait for routine maintenance.

Technical view

The source bundle describes CWE-79 reflected XSS in Softaculous Loginizer for WordPress <= 1.7.5. CVSS 3.1 is 7.1: network reachable, low complexity, no privileges required, user interaction required, and low C/I/A impact. Structured affected metadata is incomplete, so version confirmation matters.

Likely exposure

Exposure is most likely on public WordPress sites that have the Loginizer plugin installed at version 1.7.5 or earlier. The bundle does not identify CPEs or a fixed version.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with reflected XSS risk through a user-controlled browser context.

Researcher notes

Evidence is limited to the CVE description, CVSS data, and Patchstack reference. No exploit details, fixed version, CPEs, or active exploitation evidence are provided in the bundle. Avoid assuming broader Loginizer versions are affected.

Mitigation direction

  • Inventory WordPress sites for the Loginizer plugin and installed version.
  • Treat Loginizer <= 1.7.5 as vulnerable unless vendor guidance says otherwise.
  • Check Patchstack and vendor guidance for the fixed version or recommended action.
  • Update the plugin if a vendor-supported fixed release is available.
  • Disable or remove the plugin where exposure cannot be promptly remediated.

Validation and detection

  • Confirm whether each WordPress site runs Loginizer.
  • Record plugin version and compare against <= 1.7.5.
  • Review web application logs for unusual requests targeting Loginizer-related paths.
  • Verify vendor or Patchstack remediation guidance before closing the finding.
  • Retest after update or removal to confirm the vulnerable version is absent.
Prepared
Confidence
medium
Sources
3

Public sources used

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-79: User-session and phishing behavior lookup

Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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
cve · low confidence lookup

CVE-2022-45084 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
High
CVSS
7.1 (3.1)
Known Exploited
No
Published

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

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
7.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2022-45084Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SoftaculousLoginizerloginizer, n/aunaffected
Weakness

CWE details

CWE-79

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