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

CVE-2025-58843

HIGH · 7.1 CVSS v3.1 Published 2025-09-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in David Merinas Auto Last Youtube Video auto-last-youtube-video allows Stored XSS.This issue affects Auto Last Youtube Video: from n/a through <= 1.0.7.

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

A CSRF vulnerability in the Auto Last Youtube Video WordPress plugin (version <=1.0.7) allows authenticated administrators to be tricked into submitting malicious requests that store XSS payloads in the plugin settings. When other administrators view the affected pages, the stored JavaScript executes in their browsers.

MitigationUpdate to the latest plugin version when available. Until then, review admin actions in the plugin and ensure all state-changing requests validate anti-CSRF nonces.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

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 the plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'auto-last-youtube-video' or similar, or use WP-CLI: wp plugin list --search='*youtube*'
    Affected if The plugin folder exists in the WordPress installation
  2. Confirm the installed version
    Read the plugin header comment from the main PHP file in the plugin folder to extract the 'Version' field, or run: wp plugin get auto-last-youtube-video --field=version
    Affected if The version number is 1.0.7 or lower
  3. Verify the plugin is active
    Check if the plugin is enabled in WordPress via wp-admin > Plugins or use: wp plugin list --status=active --search='*youtube*'
    Affected if The plugin shows as active on the site
  4. Inspect plugin settings for suspicious content
    Navigate to the plugin settings page in wp-admin (likely under Settings or a dedicated menu item for this plugin) and examine all text fields, URLs, and configuration options for unexpected JavaScript tags, script src attributes, or encoded content that may indicate stored XSS payloads
    Affected if Any plugin setting field contains script tags, javascript: URLs, onerror/onload attributes, or other XSS vectors that were not intentionally entered by an administrator

You are affected if the Auto Last Youtube Video plugin version 1.0.7 or lower is installed and active on your WordPress site, particularly if plugin settings contain unexpected or malicious-looking content that could execute as JavaScript.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest plugin version when available. Until then, review admin actions in the plugin and ensure all state-changing requests validate anti-CSRF nonces.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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