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

CVE-2026-39603

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/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 ThemeGoods Grand Photography grandphotography allows Cross Site Request Forgery.This issue affects Grand Photography: from n/a through <= 5.7.8.

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 ThemeGoods Grand Photography WordPress theme allows attackers to trick authenticated users into performing unintended actions via malicious requests, potentially leading to unauthorized configuration changes or data modification.

MitigationImplement anti-CSRF tokens (nonce validation) on all state-changing operations and verify the Referer header or use SameSite cookie attributes to prevent cross-site request forgery attacks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Locate the Grand Photography theme files
    Search for the theme directory in your WordPress installation under wp-content/themes/ for a folder named 'grand-photography' or similar variant
    Affected if The theme directory exists and contains PHP files handling user actions
  2. Identify state-changing operations in theme PHP files
    Search theme files for form handlers, AJAX action hooks (add_action with 'wp_ajax_'), and POST/GET parameter processing that modify data
    Affected if The theme processes state-changing requests without identifying which operations are sensitive
  3. Check for nonce validation in sensitive operations
    Search for wp_nonce_field, wp_create_nonce, or check_admin_referer in files handling the sensitive operations found in step 2
    Affected if Sensitive operations lack nonce verification calls or use nonces inconsistently across all state-changing actions
  4. Verify Origin/Referer header validation
    Search theme files for $_SERVER['HTTP_ORIGIN'] or $_SERVER['HTTP_REFERER'] checks before processing sensitive requests
    Affected if The theme does not validate that requests originate from legitimate sources

You are affected if the Grand Photography theme is installed and its sensitive operations lack proper anti-CSRF nonce validation or Origin/Referer header checks.

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 state-changing operations and verify the Referer header or use SameSite cookie attributes to prevent cross-site request forgery attacks.

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-2026-39603 — 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-2026-39603 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