Skip to main content
Menu
CVEs

miniOrange's Google Authenticator unauthorized settings changes in 2FA plugin

CVE-2026-129074Published , updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 6.6.1
Who is exposed
Specific setups only

Summary

A missing authorization check in the WordPress miniOrange's Google Authenticator plugin (miniorange-2-factor-authentication) lets an attacker change its settings. An attacker can reach it remotely, but only after logging in with a low-privilege account.

Written by a model

Original description

Missing Authorization vulnerability in miniOrange miniOrange's Google Authenticator miniorange-2-factor-authentication allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects miniOrange's Google Authenticator: from n/a through 6.6.0.

Who should check

Teams running the WordPress miniOrange's Google Authenticator plugin (miniorange-2-factor-authentication) version 6.6.0 or earlier

“WordPress miniOrange's Google Authenticator Plugin <= 6.6.0 is vulnerable”

patchstack.com

What to do

  1. Check whether your setup matches what the bug needs.

    WordPress miniOrange's Google Authenticator plugin version 6.6.0 or earlier
  2. Upgrade to a fixed version: 6.6.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129074 (WordPress miniOrange's Google Authenticator plugin <= 6.6.0 - Settings Change vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129074 (entry last updated 2026-11-20):
Affected:
- miniOrange miniOrange's Google Authenticator: fixed in 6.6.1
Fixed versions: 6.6.1.
Conditions (all must be true for the bug to be hit):
- WordPress miniOrange's Google Authenticator plugin version 6.6.0 or earlier (source: https://patchstack.com/database/wordpress/plugin/miniorange-2-factor-authentication/vulnerability/wordpress-miniorange-s-google-authenticator-plugin-6-6-0-settings-change-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129074 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129074 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/miniorange-2-factor-authentication/vulnerability/wordpress-miniorange-s-google-authenticator-plugin-6-6-0-settings-change-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129074
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129074"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 22 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

Questions about CVE-2026-129074

Is CVE-2026-129074 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The plugin has a flaw that lets an attacker change the WordPress site's settings, such as disabling security features or altering configurations, which can lock the site owner out.

Source: patchstack.com

Which versions are affected by CVE-2026-129074?

miniorange-2-factor-authentication: through 6.6.0 (fixed in 6.6.1).

Source: cve.now feed data

Am I affected, and how do I check?

WordPress sites running miniOrange's Google Authenticator plugin version 6.6.0 or earlier are affected. To check, look at the plugin version shown on the Plugins screen in the WordPress admin dashboard.

Source: patchstack.com

How do I fix CVE-2026-129074?

Update the miniOrange's Google Authenticator plugin to version 6.6.1 or later, which is the listed fix.

Source: patchstack.com

No corrections so far. Something wrong on this page? Report an error.