Siteground SecurityWordPress extension · Siteground
CVE-2022-0993
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 · uneditedThe SiteGround Security plugin for WordPress is vulnerable to authentication bypass that allows unauthenticated users to log in as administrative users due to missing identity verification on the 2FA back-up code implementation that logs users in upon success. This affects versions up to, and including, 1.2.5.
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 confidenceThe SiteGround Security WordPress plugin fails to properly verify identity when processing 2FA backup codes, allowing unauthenticated attackers to bypass authentication entirely and gain administrative access by submitting valid backup codes without proving they are the legitimate user.
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
Siteground SecurityWordPress extension
<= 1.2.5CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate the SiteGround Security plugin installationCheck your WordPress wp-content/plugins/ directory for a folder named 'siteground-security' or 'siteground-security-plugin', or view the installed plugins list in WordPress admin under Plugins > Installed PluginsAffected if The SiteGround Security plugin is present on the WordPress site
-
Determine the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and find the SiteGround Security plugin entry to view the version number, or inspect the main plugin file (usually siteground-security.php) and look for the 'Version' header in the plugin commentsAffected if The version listed is 1.2.5 or lower
-
Verify if 2FA with backup codes is configuredCheck the SiteGround Security plugin settings in WordPress admin under SiteGround Security > 2FA or similar settings page, or examine the wp_options table for records related to 'sg_security_2fa' or 'backup_codes' configurationAffected if Two-factor authentication or backup codes feature is enabled for any user account
-
Audit user accounts for unauthorized administrative accessNavigate to WordPress admin under Users > All Users and review the list of administrators, checking for any unfamiliar accounts or recent privilege escalations, or query the wp_users and wp_usermeta tables for accounts with administrator role created after the plugin was installedAffected if Unexpected administrator accounts exist or administrative privileges were granted to unknown users
Your site is affected if SiteGround Security plugin version 1.2.5 or lower is installed with 2FA or backup codes functionality enabled, regardless of whether exploitation is confirmed.
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 · scopedUpdate the SiteGround Security plugin to the latest patched version immediately. If no patched version is available, disable the plugin and consider alternative security solutions. Audit user accounts for unauthorized administrative access after patching.
SiteGround Security version 1.2.6 or later
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the SiteGround Security plugin
- Check if an update is available and install it
- Verify the plugin has been updated to version 1.2.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Siteground Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0993 — 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-0993 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