dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-7684

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

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 Last.fm Recent Album Artwork plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.2. This is due to missing or incorrect nonce validation on the 'lastfm_albums_artwork.php' page. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Last.fm Recent Album Artwork WordPress plugin versions up to 1.0.2 lack proper nonce validation on the 'lastfm_albums_artwork.php' settings page, enabling unauthenticated attackers to forge administrative requests that can modify plugin settings and inject malicious scripts.

MitigationUpdate to version 1.0.3 or later when available; audit the plugin settings for unauthorized changes; disable the plugin if no update is available.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Last.fm Recent Album Artwork' or check the wp-content/plugins directory for a folder named 'lastfm-recent-album-artwork' or similar
    Affected if Plugin is not installed on the WordPress site
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins and find the Last.fm Recent Album Artwork plugin; the version number is displayed below the plugin name. Alternatively, open the main plugin PHP file and look for the 'Version' header comment
    Affected if Version is 1.0.2 or lower (versions up to and including 1.0.2 are affected)
  3. Inspect the vulnerable settings file
    Locate the file 'lastfm_albums_artwork.php' in the plugin directory and examine it for nonce validation; look for wp_nonce_field() or check_admin_referer() calls around any form handling or settings updates
    Affected if The file exists and lacks proper nonce validation on settings forms
  4. Review plugin settings for tampering
    Access the plugin settings page (usually under Settings > Last.fm Albums Artwork or similar) and check all fields for suspicious values, especially any fields containing script tags, eval(), or unfamiliar URLs
    Affected if Plugin settings contain unexpected JavaScript, iframes, or point to unknown external resources

The site is affected if the Last.fm Recent Album Artwork plugin is installed at version 1.0.2 or lower, as the missing nonce validation allows unauthenticated modification of settings.

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 version 1.0.3 or later when available; audit the plugin settings for unauthorized changes; disable the plugin if no update is available.

Recommended fix Moderate confidence

1.0.3

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Last.fm Recent Album Artwork' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/lastfm-recent-album-artwork/ and upload manually
  6. 6. Verify the updated version number after installation

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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