Dynamic Xml Sitemaps Generator For GoogleWordPress extension · Wpgrim
CVE-2023-26514
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 WPGrim Dynamic XML Sitemaps Generator for Google plugin <= 1.3.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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the WPGrim Dynamic XML Sitemaps Generator for Google WordPress plugin versions 1.3.3 and below allows attackers to trick authenticated administrators into performing unintended actions (such as modifying sitemap settings or triggering sitemap generation) by crafting malicious requests that the victim's browser automatically submits due to lack of proper token validation.
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
Dynamic Xml Sitemaps Generator For GoogleWordPress extension
<= 1.3.3CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify the plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WPGrim Dynamic XML Sitemaps Generator for Google' in the list.Affected if The plugin appears in the installed plugins list
-
Check the installed plugin versionIn the Plugins list, locate the plugin and view the version number displayed below the plugin name, or check the plugin's main PHP file header for the Version tag.Affected if The version is 1.3.3 or lower (any version up to and including 1.3.3)
-
Confirm the plugin is activeIn WordPress admin > Plugins, verify the plugin status shows 'Active' rather than 'Inactive' or 'Must-Use'.Affected if The plugin status is Active
-
Identify accessible admin endpointsCheck if you can access the plugin's settings page under Settings > XML Sitemap (or similar) or trigger sitemap generation actions while logged in as administrator.Affected if Administrative functions are accessible and the site relies on this plugin for sitemap generation
The environment is affected if the WPGrim Dynamic XML Sitemaps plugin is installed, active, and running version 1.3.3 or lower.
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 AJAX endpoints within the plugin, and verify the request origin server-side before processing any administrative actions.
Fix this in Dynamic Xml Sitemaps Generator For Google
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26514 — 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-2023-26514 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