dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64632

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Auctollo Google XML Sitemaps google-sitemap-generator allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Google XML Sitemaps: from n/a through <= 4.1.22.

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

Missing authorization vulnerability in Auctollo Google XML Sitemaps plugin allows attackers to exploit incorrectly configured access control security levels. The plugin fails to properly enforce authorization checks, potentially enabling unauthorized access to sitemap generation functionality.

MitigationUpdate to the latest version of the Google XML Sitemaps plugin when available. Review and enforce proper authorization controls on all plugin endpoints and functionality.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Google XML Sitemaps plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for the google-xml-sitemaps folder
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate the Google XML Sitemaps plugin to view its version number, or check the main plugin PHP file for the Version header comment
    Affected if The version number falls within an unpatched range (version prior to the fix being applied)
  3. Test unauthenticated access to sitemap generation
    Attempt to access the sitemap endpoint directly without logging in: visit /sitemap.xml, /sitemap_index.xml, or the default sitemap URL configured in the plugin settings
    Affected if The sitemap loads successfully without any authentication or authorization challenge
  4. Verify access control configuration
    Check the plugin settings under Settings > XML-Sitemap for any option that controls who can access or generate sitemaps; review if the plugin has any capability or role-based restrictions configured
    Affected if No authorization restrictions are enforced or configurable options are missing/unenforced

A user is affected if the Google XML Sitemaps plugin is installed and the sitemap generation functionality can be accessed by unauthenticated users without proper authorization checks being enforced.

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

Update to the latest version of the Google XML Sitemaps plugin when available. Review and enforce proper authorization controls on all plugin endpoints and functionality.

Recommended fix Moderate confidence

Version 4.1.23 or later (verify latest stable release on WordPress plugin repository)

  1. 1. Check the current version of the Google XML Sitemaps plugin installed on your WordPress site.
  2. 2. Navigate to the WordPress admin dashboard, go to Plugins > Installed Plugins.
  3. 3. Locate the 'Google XML Sitemaps' plugin and note the current version number.
  4. 4. Visit the official WordPress plugin repository or the developer's website to verify the latest available version.
  5. 5. If version 4.1.23 or higher is available, update the plugin to that version to remediate the missing authorization vulnerability.
  6. 6. After updating, verify the plugin functions correctly and check that the sitemap still generates properly.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64632 — 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-2025-64632 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