Google AuthenticatorWordPress extension · Miniorange
CVE-2022-4943
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 miniOrange's Google Authenticator plugin for WordPress is vulnerable to authorization bypass due to a missing capability check when changing plugin settings in versions up to, and including, 5.6.5. This makes it possible for unauthenticated attackers to change the plugin's settings.
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 miniOrange Google Authenticator plugin for WordPress lacks proper authorization checks on settings change endpoints, allowing unauthenticated users to modify plugin configuration. This authorization bypass stems from missing capability checks (like current_user_can('manage_options')) before processing settings updates.
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
Google AuthenticatorWordPress extension
<= 5.6.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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm WordPress installationLook for wp-config.php in the web root or check for wp-content/plugins directory existenceAffected if WordPress is not present - the plugin cannot be exploited in isolation
-
Identify miniOrange Google Authenticator pluginCheck for the presence of wp-content/plugins/miniorange-google-authenticator directoryAffected if The plugin directory does not exist - not affected
-
Determine installed plugin versionOpen the main plugin file (miniorange-google-authenticator.php) and read the Version header in the plugin comment block, or check the plugin version from WordPress admin plugins listAffected if Version is 5.6.5 or lower
-
Verify plugin is activeCheck WordPress admin under Plugins > Installed Plugins, or query the wp_options table for option_name='active_plugins' containing 'miniorange-google-authenticator'Affected if Plugin is not active - the vulnerability cannot be triggered
-
Test unauthenticated settings accessSend a POST request to the plugin's admin-ajax.php endpoint or settings page URL without authenticating (no valid session cookie), observing whether the request is processed without a 401/403 errorAffected if Request is processed without authentication required - vulnerability is present and exploitable
If WordPress is running with miniOrange Google Authenticator plugin installed, active, and version 5.6.5 or lower, the environment is affected by this authorization bypass 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.
From vendor dataUpdate the miniOrange Google Authenticator plugin to version 5.6.6 or later, which includes the missing capability check. If immediate update is not possible, consider restricting access to the affected endpoints at the web server level.
Fix this in Google Authenticator
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-4943 — 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-4943 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