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

CVE-2026-39635

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 Magazine grandmagazine allows Cross Site Request Forgery.This issue affects Grand Magazine: from n/a through <= 3.5.5.

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 Magazine WordPress theme (versions <= 3.5.5) allows remote attackers to induce authenticated administrators to perform unintended state-changing actions like modifying settings or content.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing operations (forms, AJAX endpoints, admin actions) and validate request Referer/Origin headers to ensure requests originate from trusted domains.

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. Identify if Grand Magazine theme is installed
    Navigate to WordPress Admin > Appearance > Themes, or inspect wp-content/themes/ directory for grand-magazine folder
    Affected if Grand Magazine theme is present in the WordPress installation
  2. Determine installed theme version
    Check theme style.css header for Version: field, or look in WordPress Admin > Appearance > Theme Details
    Affected if Any version of Grand Magazine theme is installed (no version range specified for fix)
  3. Locate theme files handling settings or content changes
    Search in wp-content/themes/grand-magazine/ for PHP files containing form handlers, AJAX actions, or settings update logic (e.g., functions.php, options.php, or files with 'update_option', 'save', 'settings' keywords)
    Affected if The theme contains files that process state-changing requests
  4. Inspect for nonce validation presence
    Open the identified settings/content-handling PHP files and search for 'wp_verify_nonce', 'check_admin_referer', or 'wp_nonce_field' function calls
    Affected if These nonce validation functions are absent from files that process administrator actions
  5. Verify CSRF token usage on form submissions
    If nonce functions are missing, manually inspect form definitions in the theme for missing nonce token fields and verify that $_POST or $_REQUEST data is processed without verification
    Affected if Forms modifying theme settings or content lack nonce token validation and process requests directly

If the Grand Magazine theme is installed and its settings/content-modification handlers lack wp_verify_nonce or equivalent CSRF token checks, the environment is vulnerable to CVE-2026-39635.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonces (anti-CSRF tokens) on all state-changing operations (forms, AJAX endpoints, admin actions) and validate request Referer/Origin headers to ensure requests originate from trusted domains.

Recommended fix Moderate confidence

Grand Magazine latest version (contact ThemeGoods for exact version number containing the fix)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Deactivate the current Grand Magazine theme (version 3.5.5 or lower)
  4. Delete the vulnerable Grand Magazine theme
  5. Install the latest version of Grand Magazine theme from a trusted source (ThemeGoods official website or WordPress repository)
  6. Activate the new theme
  7. Verify the theme is functioning correctly and review site functionality
Caveat Review theme settings after upgrade as configuration may need adjustment

Generated from the published advisory — verify against the referenced sources before acting.

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