CVE-2026-39633
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in ThemeGoods Grand Car Rental grandcarrental allows Cross Site Request Forgery.This issue affects Grand Car Rental: from n/a through <= 3.6.9.
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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in ThemeGoods Grand Car Rental WordPress theme allows attackers to trick authenticated administrators into unknowingly executing unwanted actions, such as modifying plugin settings or performing administrative operations, by forcing their browser to send malicious requests.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Grand Car Rental theme filesInspect the wp-content/themes/ directory for a folder named 'grandcarrental', 'grand-car-rental', or similar themename containing 'grand car rental' or 'themegoods'Affected if The theme folder exists in the themes directory
-
Identify the installed versionOpen the theme's style.css file in the theme folder and locate the 'Version:' header in the CSS comment block at the topAffected if The version listed is 3.6.9 or lower, or if no version is displayed and the theme appears to be the Grand Car Rental theme from ThemeGoods
-
Confirm the theme is activeCheck the site's active theme via WordPress admin appearance > themes, or inspect the wp_options table for 'template' or 'stylesheet' values matching the theme folder nameAffected if The Grand Car Rental theme is currently active on the site
-
Inspect state-changing PHP handlers for nonce validationExamine PHP files that handle POST, PUT, or DELETE requests (such as booking-processing, settings-saving, or user-management files) for the presence of 'wp_verify_nonce' or 'check_admin_referer' function calls before processingAffected if State-changing operations lack nonce verification logic, meaning forms or AJAX endpoints process requests without validating anti-CSRF tokens
-
Check form and AJAX submissions for nonce fieldsInspect theme templates containing forms (booking forms, settings forms) and JavaScript files handling AJAX requests to verify they include nonce values (typically passed as a hidden field or in wp_localize_script data)Affected if Forms and AJAX handlers do not include nonce parameters, leaving requests vulnerable to CSRF
You are affected if the ThemeGoods Grand Car Rental theme version 3.6.9 or below is installed and active, and state-changing operations in the theme code lack proper nonce verification.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF nonce tokens on all state-changing forms and validate Origin/Referer headers; for WordPress themes, use wp_nonce_field() and check capabilities with current_user_can() before processing requests.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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