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

CVE-2025-26931

HIGH · 7.1 CVSS v3.1 Published 2025-02-25
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 Tribulant Software Tribulant Gallery Voting gallery-voting allows Stored XSS.This issue affects Tribulant Gallery Voting: from n/a through <= 1.2.1.

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

CSRF vulnerability in Tribulant Gallery Voting plugin enables attackers to inject malicious scripts via stored XSS. An attacker can craft a malicious link that, when clicked by an authenticated user with appropriate privileges, causes the victim's browser to submit a request that stores XSS payload in the gallery voting data. Since the XSS is stored, it executes for all users viewing the affected gallery content.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and AJAX requests in the plugin, add proper input validation and sanitization for all user-supplied data, and update to the latest patched version if 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
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 Tribulant Gallery Voting plugin is installed
    Check your WordPress plugins directory or admin panel for the 'Gallery Voting' plugin by Tribulant. Look for the plugin file in wp-content/plugins/ or check via WordPress admin > Plugins.
    Affected if The plugin is installed and active in WordPress
  2. Determine installed plugin version
    Check the plugin main file (usually gallery-voting.php or similar) for the version comment header, or view the plugin details in WordPress admin > Plugins. Compare this version against the affected version range if known.
    Affected if Version is within an affected range or unknown/older version
  3. Confirm voting functionality is enabled
    Check if any gallery has the voting feature activated. Look in Gallery settings or widget configuration where 'voting' or 'allow voting' options exist.
    Affected if Voting feature is enabled on one or more galleries
  4. Inspect for CSRF protection in form submissions
    Examine the plugin PHP files for presence of nonce verification (wp_verify_nonce, check_admin_referer) on AJAX requests and form handlers related to voting submissions. Search for 'nonce' or '_wpnonce' in gallery voting PHP files.
    Affected if No nonce/CSRF token validation is found in voting submission handlers

A user is affected if the Tribulant Gallery Voting plugin is installed, the voting feature is enabled, and the plugin lacks proper CSRF nonce protection in its voting submission code.

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 (nonces) on all form submissions and AJAX requests in the plugin, add proper input validation and sanitization for all user-supplied data, and update to the latest patched version if available.

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