LoginizerWordPress extension
CVE-2022-45084
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in Softaculous Loginizer plugin <= 1.7.5 versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn unauthenticated reflected Cross-Site Scripting (XSS) vulnerability exists in the Softaculous Loginizer WordPress plugin versions 1.7.5 and below. The vulnerability allows attackers to inject malicious JavaScript code through unsanitized user input that gets reflected back in the application's response.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LoginizerWordPress extension
< 1.7.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Loginizer plugin is installedLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the plugins directory via file system access to confirm the Loginizer plugin is present.Affected if The Loginizer plugin is installed and active on the WordPress site.
-
Check installed Loginizer versionIn WordPress admin, locate the Loginizer plugin in the plugins list and note the version number displayed, or check the plugin header in the main plugin file (typically loginizer.php) for the Version field.Affected if The installed version is 1.7.5 or lower (versions below 1.7.6 are affected).
-
Confirm version is within vulnerable rangeCompare your installed version against the affected range: versions less than 1.7.6 are vulnerable. If you are running 1.7.6 or higher, you are not affected by this CVE.Affected if The installed version is < 1.7.6, meaning the plugin is vulnerable to the reflected XSS.
A WordPress site running the Loginizer plugin version 1.7.5 or below is affected by this unauthenticated reflected XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.7.6
Update the Loginizer plugin to a version higher than 1.7.5. Until then, consider disabling the plugin or implementing web application firewall rules to filter malicious request parameters.
1.7.6
- Update Loginizer plugin to version 1.7.6 or later through the WordPress plugin dashboard, or replace the plugin files with version 1.7.6 from the WordPress plugin repository
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Loginizer
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-45084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-45084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data