CVE-2025-23567
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 Tamer Ziady GDReseller gdreseller allows Stored XSS.This issue affects GDReseller: from n/a through <= 1.6.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in GDReseller enables attackers to inject malicious scripts that persist (Stored XSS) by tricking authenticated users into submitting crafted requests. This allows execution of arbitrary JavaScript in other users' browsers when the stored payload is rendered.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GDReseller plugin installationIn WordPress admin, navigate to Plugins > Installed Plugins and locate GDReseller, or check the plugin files in /wp-content/plugins/ directory for the gd-reseller folderAffected if GDReseller plugin is not installed on the WordPress site
-
Identify installed GDReseller versionCheck the plugin header in gd-reseller.php for the 'Version' field, or view the plugin details in WordPress admin plugin listAffected if Version cannot be determined or is within any affected range (if known)
-
Locate state-changing forms in GDResellerInspect plugin source code for forms that modify data: look for <form> tags in PHP files within the plugin directory, especially those handling reseller settings, user submissions, or content updatesAffected if Forms exist that accept user input withoutevident nonce validation
-
Verify CSRF protection presenceSearch plugin PHP files for 'wp_nonce_field', 'wp_verify_nonce', 'check_admin_referer', or 'nonce' parameters in form handling codeAffected if No anti-CSRF tokens or nonce verification found in form processing logic
-
Check input handling for stored dataExamine how form submissions are saved to the database; look for add_post_meta, update_option, insert into database calls, or any function that stores user inputAffected if User-supplied input is stored without sanitization (lack of sanitize_text_field, esc_html, esc_attr, or similar functions)
The site is affected if GDReseller is installed and forms lack CSRF token validation and proper input sanitization, allowing stored XSS payloads to persist and execute in other users browsers.
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 tokens on all state-changing forms and validate Origin/Referer headers; apply proper input sanitization and output encoding to prevent stored XSS execution.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23567 — 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-2025-23567 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