dbcve.org
GalleriaWordPress extension · Galleria Project

CVE-2023-35780

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to after 1.0.3 or later.
See remediation →
72/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
Cross-Site Request Forgery (CSRF) vulnerability in Andy Whalen Galleria plugin <= 1.0.3 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 Andy Whalen Galleria plugin versions 1.0.3 and below allows attackers to trick authenticated users into unknowingly submitting malicious requests, potentially leading to unauthorized actions within the plugin.

MitigationImplement anti-CSRF tokens (nonces) for state-changing operations and validate Origin/Referer headers to ensure requests originate from trusted sources.

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
GalleriaWordPress extension
Affected:<= 1.0.3

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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. Identify if Galleria plugin is installed
    Check the WordPress plugin directory or plugin management interface for the presence of the Galleria plugin by Andy Whalen
    Affected if Galleria plugin is not found in the installation
  2. Determine the installed Galleria plugin version
    Access the plugin details page in the CMS admin panel or inspect the plugin's main PHP file header for the version declaration
    Affected if The version is 1.0.3 or lower, or if the version cannot be determined (plugin is outdated/unmaintained)
  3. Verify the plugin is active
    Check the plugin status in the CMS admin panel under the plugins list
    Affected if The plugin is installed and currently activated on the site
  4. Identify state-changing operations without CSRF protection
    Review plugin source code for form submissions and AJAX actions, specifically look for missing wp_verify_nonce, check_ajax_referer, or nonce verification calls before processing state-changing requests
    Affected if Any admin or user-facing actions in the plugin process requests without validating a CSRF token

A site is affected if the Galleria plugin versions 1.0.3 or below is installed and active, with state-changing operations lacking nonce verification.

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 1.0.3
Interim mitigation

Implement anti-CSRF tokens (nonces) for state-changing operations and validate Origin/Referer headers to ensure requests originate from trusted sources.

Fix this in Galleria Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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