dbcve.org
Alt Text AiWordPress extension · Alttext

CVE-2025-46232

HIGH · 8.8 CVSS v3.1 Published 2025-04-22
Fix available
A fix is available. Upgrade to 1.9.94 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Missing Authorization vulnerability in alttextai Download Alt Text AI alttext-ai allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Download Alt Text AI: from n/a through <= 1.9.93.

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 · moderate confidence

Missing Authorization vulnerability in the alttext-ai WordPress plugin allows exploitation of incorrectly configured access control security levels, potentially enabling unauthenticated or lower-privileged users to access sensitive administrative functions or download alt text data they should not have permission to access.

MitigationImplement proper capability checks and authorization validation on all sensitive endpoints, AJAX actions, and download functions within the plugin to ensure users have appropriate privileges before executing operations.

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
Alt Text AiWordPress extension
Affected:< 1.9.94

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Verify alttext-ai plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the alttext-ai or alttext-alt-text-ai folder, or query the wp_options table for the active_plugins option to see if the plugin is registered.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin is listed in active_plugins in the database.
  2. Determine installed plugin version
    Read the main plugin file header in wp-content/plugins/[plugin-folder]/alttext-ai.php to find the 'Version' tag, or check the WordPress plugin administration page for the installed version.
    Affected if The version number is less than 1.9.94 (e.g., 1.9.93, 1.9.0, etc.).
  3. Identify sensitive AJAX actions
    Search the plugin source code for wp_ajax_ and wp_ajax_nopriv_ hooks to locate all registered AJAX endpoints. Examine the callback functions to see if they perform sensitive operations like administrative functions or data downloads.
    Affected if The plugin registers AJAX actions that perform sensitive operations without calling current_user_can() or checking user capabilities.
  4. Check download function authorization
    Examine the plugin code for functions handling file or data downloads (look for terms like 'download', 'export', 'file', 'attachment'). Verify if these functions validate user capabilities before serving content.
    Affected if Download or export functions can be accessed without proper capability verification or authentication.
  5. Test endpoint accessibility
    If possible, attempt to access known plugin endpoints (such as AJAX action URLs at /wp-admin/admin-ajax.php) as an unauthenticated user or a low-privilege user (subscriber role). Check if requests are accepted without rejection or capability failure.
    Affected if Sensitive administrative functions or data retrieval endpoints respond successfully to unauthenticated or low-privileged user requests.

The environment is affected if the alttext-ai plugin version is below 1.9.94 AND sensitive AJAX endpoints or download functions lack proper capability checks, allowing unauthorized access.

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
Upgrade available Upgrade to 1.9.94 or later
Fixed in 1.9.94
Interim mitigation

Implement proper capability checks and authorization validation on all sensitive endpoints, AJAX actions, and download functions within the plugin to ensure users have appropriate privileges before executing operations.

Recommended fix High confidence

Version 1.9.94 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Alt Text Ai' or 'Download Alt Text AI' plugin
  4. If an update to version 1.9.94 or higher is available, click 'Update Now'
  5. Alternatively, manually download version 1.9.94 or later from the WordPress plugin repository or vendor
  6. Deactivate and delete the old plugin version
  7. Upload and install the new version
  8. Reactivate the plugin
Caveat None documented in the provided information; minor plugin version updates typically retain compatibility

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

Fix this in Alt Text Ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46232 — 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-46232 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