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

CVE-2025-26550

HIGH · 7.1 CVSS v3.1 Published 2025-02-13
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 Kunal Shivale Global Meta Keyword & Description global-meta-keyword-and-description allows Stored XSS.This issue affects Global Meta Keyword & Description: from n/a through <= 2.3.

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 Global Meta Keyword & Description WordPress plugin allows attackers to inject malicious scripts through the plugin's meta keyword and description fields. Since the vulnerability enables Stored XSS, any injected JavaScript will persist and execute whenever the affected meta fields are rendered on the site frontend or admin pages, potentially compromising administrator sessions and site visitors.

MitigationImplement anti-CSRF tokens (nonce validation) on all form submissions in the plugin and ensure proper sanitization of input and escaping of output for meta keyword/description fields. Update to the latest plugin version if available, or disable the plugin until a patched version is released.

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. Verify WordPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Global Meta Keyword & Description' or check the /wp-content/plugins/ directory for a folder containing 'global-meta' or similar naming
    Affected if The plugin is installed and active on the WordPress site
  2. Identify plugin version
    In WordPress admin > Plugins, find the plugin and view the version number under the plugin name, or inspect the plugin's main PHP file header for 'Version:' tag
    Affected if Version is unknown, older than current, or cannot be determined (assume affected)
  3. Check meta field accessibility
    Navigate to the plugin settings page (usually under Settings or a dedicated plugin menu) and locate the meta keyword and description input fields
    Affected if The plugin provides input fields for meta keywords and descriptions that can be saved
  4. Inspect stored meta values in database
    Access WordPress database via phpMyAdmin or WP-CLI and query the wp_postmeta table for meta keys like '_meta_keywords', '_meta_description', or plugin-specific custom fields; also check wp_options for plugin settings
    Affected if Meta keyword or description fields contain unsanitized content with script tags (<script>, javascript:, etc.)
  5. Verify CSRF protection is missing
    Inspect the plugin's PHP source code (in wp-content/plugins/) and examine form handling for nonce validation - look for wp_verify_nonce, check_admin_referer, or nonce_field functions in the settings save handler
    Affected if No nonce verification or CSRF tokens are present in the plugin's form submission handling code

The site is affected if the Global Meta Keyword & Description plugin is installed and active, particularly if the plugin lacks proper nonce validation in its forms and if the meta fields can be modified without CSRF protection.

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

Implement anti-CSRF tokens (nonce validation) on all form submissions in the plugin and ensure proper sanitization of input and escaping of output for meta keyword/description fields. Update to the latest plugin version if available, or disable the plugin until a patched version is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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