dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-14367

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The Easy Theme Options plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.0. This is due to missing authorization checks in the eto_import_settings function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to import arbitrary plugin settings via the 'eto_import_settings' parameter.

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 confidence

The Easy Theme Options WordPress plugin versions up to 1.0 lacks authorization checks in the eto_import_settings function, allowing any authenticated user with Subscriber-level access or higher to import arbitrary plugin settings through the eto_import_settings parameter.

MitigationUpdate to a patched version when available; if no patch exists, disable the plugin or add proper capability checks and nonce verification to the eto_import_settings function.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Easy Theme Options plugin is installed
    Check the WordPress plugin directory for 'easy-theme-options' folder or view installed plugins in wp-admin under Plugins > Installed Plugins
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    Check the plugin's main PHP file (usually easy-theme-options.php) for the 'Version' header in the plugin comments, or view version in Plugins > Installed Plugins
    Affected if The version is 1.0 or earlier (the affected version range)
  3. Verify eto_import_settings function exists
    Search the plugin's main PHP file for the function 'eto_import_settings' - look for function definition like 'function eto_import_settings()'
    Affected if The function exists in the plugin code
  4. Check if authorization is enforced on the import function
    Examine the eto_import_settings function for capability checks (look for 'current_user_can', 'manage_options', or similar authorization calls) and nonce verification (look for 'wp_verify_nonce' or 'check_admin_referer')
    Affected if No capability check (e.g., current_user_can('manage_options')) and no nonce verification are found before the import logic executes

The environment is affected if the Easy Theme Options plugin version 1.0 or earlier is installed AND the eto_import_settings function lacks proper authorization checks and nonce verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available; if no patch exists, disable the plugin or add proper capability checks and nonce verification to the eto_import_settings function.

Recommended fix Moderate confidence

Latest version available after 1.0 (check WordPress plugin repository for the current stable release)

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the Easy Theme Options plugin in the list
  3. 3. Check if an update is available for the plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version that includes the authorization fix
  5. 5. After updating, verify the plugin is functioning correctly on the site
  6. 6. Confirm that Subscriber-level users can no longer access import functionality without proper authorization

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14367 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14367 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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