dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13603

HIGH · 8.8 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The WP AUDIO GALLERY plugin for WordPress is vulnerable to Unauthorized Arbitrary File Read in all versions up to, and including, 2.0. This is due to insufficient capability checks and lack of nonce verification on the "wpag_htaccess_callback" function This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the site's .htaccess file with arbitrary content, which can lead to arbitrary file read on the server under certain configurations.

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 WP AUDIO GALLERY WordPress plugin (versions up to 2.0) has a missing capability check and no nonce verification in the wpag_htaccess_callback function. This allows any authenticated user with subscriber-level permissions to overwrite the site's .htaccess file with arbitrary content, potentially leading to arbitrary file read on the server.

MitigationUpdate to a patched version of the plugin if available, or remove the plugin until a fix is released. If immediate remediation is required, implement proper capability checks (e.g., current_user_can('manage_options')) and nonce verification in the wpag_htaccess_callback 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
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. Identify if WP AUDIO GALLERY plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP AUDIO GALLERY' in the installed plugins list
    Affected if The plugin appears in the installed plugins list, regardless of activation status
  2. Determine the installed plugin version
    Click on the plugin name in the Plugins list to view its details, or inspect the main plugin file header for the 'Version' field
    Affected if The version is 2.0 or lower (the vulnerability affects versions up to 2.0)
  3. Verify the vulnerable function exists
    Locate the plugin files via FTP or file manager, then search for 'wpag_htaccess_callback' in the plugin code to confirm the function exists
    Affected if The function wpag_htaccess_callback is present in the plugin files
  4. Confirm the permission vulnerability
    Review the code around wpag_htaccess_callback to check for missing current_user_can() capability checks and missing nonce verification (check for wp_verify_nonce or similar)
    Affected if No capability check (like current_user_can('manage_options')) and no nonce verification are found before the .htaccess write operation

A user is affected if the WP AUDIO GALLERY plugin is installed at version 2.0 or lower and the code lacks proper capability checks and nonce validation on the wpag_htaccess_callback function.

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 of the plugin if available, or remove the plugin until a fix is released. If immediate remediation is required, implement proper capability checks (e.g., current_user_can('manage_options')) and nonce verification in the wpag_htaccess_callback function.

Recommended fix Moderate confidence

Latest version above 2.0 (check WordPress Plugin Repository for current release)

  1. 1. Log in to WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WP AUDIO GALLERY' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update appears, manually download the latest version from the WordPress Plugin Repository (plugins.trac.wordpress.org) and reinstall
  6. 6. After updating, verify the site still functions correctly

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-13603 — 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-13603 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