Google Xml Sitemap For VideosWordPress extension · Digitalinspiration

CVE-2023-25055

HIGH · 8.8 CVSS v3.1 Published 2023-06-15
Fix available
A fix is available. Upgrade to after 2.6.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Amit Agarwal Google XML Sitemap for Videos plugin <= 2.6.1 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Google XML Sitemap for Videos WordPress plugin allows remote attackers to induce authenticated administrators to perform unintended actions by tricking them into submitting malicious requests.

MitigationUpdate the plugin to the latest patched version once released, or implement anti-CSRF tokens on all form submissions and AJAX endpoints within the plugin.

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
Google Xml Sitemap For VideosWordPress extension
Affected:<= 2.6.1

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check if the Google XML Sitemap for Videos plugin is installed
    Log in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Google Xml Sitemap For Videos' or 'Digitalinspiration'
    Affected if The plugin does not appear in the installed plugins list
  2. Verify the installed version number
    In the Plugins page, look for the version number displayed below the plugin name in the list, or click on the plugin and check its details
    Affected if The displayed version is 2.6.1 or lower
  3. Confirm the plugin is active
    On the Plugins page, check if the plugin shows 'Active' status or 'Activate' link
    Affected if The plugin is active (CSRF only affects authenticated administrators using the plugin)
  4. Compare against affected version range
    Document the exact version number found and compare: affected versions are <= 2.6.1
    Affected if Installed version is 2.6.1 or any lower version number

You are affected if the Google XML Sitemap for Videos plugin is installed, active, and running version 2.6.1 or lower.

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
Upgrade available Upgrade to a release after 2.6.1
Interim mitigation

Update the plugin to the latest patched version once released, or implement anti-CSRF tokens on all form submissions and AJAX endpoints within the plugin.

Fix this in Google Xml Sitemap For Videos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2023-25055 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