Skip to main content
WordPress plugin recordReviewed

XML Sitemap Generator vulnerability history and options-page checks

The records here concern a plugin whose options page is under Settings > XML-Sitemap.

Match your version to each record, then check what the sitemap lists, which rules put it there and which search engines the site notifies.

XML Sitemap Generator vulnerability history

Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 3 records for XML Sitemap Generator. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.

Update to at least version 4.1.23

Worked out from data retrieved on .

Every affected range listed in this source for XML Sitemap Generator ends before version 4.1.23.

A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.

  1. Google XML Sitemaps <= 4.1.22 - Missing Authorization

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.3)
    Affected versions
    • All versions up to and including 4.1.22

    Patched versions: 4.1.23

    Update to at least version 4.1.23.

  2. XML Sitemaps <= 4.1.1 - Authenticated (Admin+) Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 4.1.1

    Patched versions: 4.1.2

    Update to at least version 4.1.2.

  3. XML Sitemaps <= 4.0.9 - Authenticated Cross-Site Scripting

    Published:
    Last updated:
    Severity:
    Medium (CVSS 5.5)
    Affected versions
    • All versions up to and including 4.0.9

    Patched versions: 4.1.0

    Update to at least version 4.1.0.

Check XML Sitemap Generator on a live site

Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.

The XML Sitemap Generator options page and its typed fields

XML Sitemap Generator for Google, published on WordPress.org by Auctollo, generates XML and HTML sitemaps.

Its options page is under Settings > XML-Sitemap, the listing says. The vendor's help page describes fields there that take typed values, among them Additional Pages, for files or URLs that are not part of the WordPress blog, and post IDs to exclude.

CVE-2021-25088 has a title that includes the words "Authenticated (Admin+)". Separately, WordPress's roles page says an Administrator has access to all administration features within a single site.

XML Sitemap Generator security records, including those titled Google XML Sitemaps and XML Sitemaps

The titles quoted in this section begin "Google XML Sitemaps" or "XML Sitemaps".

The plugin's listing is headed XML Sitemap Generator for Google. Match on the version fields.

Two of those titles end in Cross-Site Scripting. CVE-2021-25088 has a title ending "Authenticated (Admin+) Cross-Site Scripting" (affected: all versions up to and including 4.1.1; patched: 4.1.2). CVE-2018-16204 has a title ending "Authenticated Cross-Site Scripting" (affected: all versions up to and including 4.0.9; patched: 4.1.0).

CVE-2025-64632 has a title ending "Missing Authorization" (affected: all versions up to and including 4.1.22; patched: 4.1.23). The plugin's changelog on WordPress.org names the same CVE id in its entry for 4.1.23, where the vendor writes of "unauthenticated users from modifying plugin settings". Those words are the changelog's, not the record's.

Five read-only checks, from the Plugins screen to robots.txt

All five can be done by reading.

On Settings > XML-Sitemap, leave without pressing Update Options, the button the help page names at the end of that page.

Changelog entries and the installed version

Start with the changelog on the plugin's WordPress.org listing. Some of its entries mark security changes in the vendor's own words, and one asks sites that copied the Nginx rules from Settings > XML-Sitemap into their nginx config to re-copy the updated block. Read it beside the update guidance at the top of the history.

Then, on the Plugins screen, note the version number in the Description column, the Automatic update column's entry, and the update notice WordPress displays when the Plugin Directory holds a newer version.

Sitemap contents

The listing gives the sitemap's address as the site URL followed by /sitemap.xml; the help page describes options that override the file name and base URL. Request it and note every address that should not be advertised. The help page ties sitemap-externals.xml to the external pages entered under Additional Pages, so read that file entry by entry.

URL inclusion rules

Look in three places. The options page: the help page describes Sitemap Content, Exclude Items and Additional Pages, so copy each as it stands. The robots.txt file: by default, the help page says, the plugin will omit any URLs that appear in it. And code: from version 4.1.20, it says, the generator can be customised with filters in the theme's functions.php file or a separate plugin.

Every filter name it lists begins sm_, so search the theme and any site-specific plugin for that prefix and record each match.

Search engine notifications

Under Search Engine Updates, the help page describes Notify Google about updates of your Blog, Notify Bing about updates of your Blog and Add sitemap URL to the virtual robots.txt file. Record which your version shows and which are ticked, then open /robots.txt and note whether the sitemap's address appears.

Administration access

On the Users screen, the Role column and role filter links show who holds each role: record every Administrator. WordPress's roles page says capabilities can be assigned to or removed from a role, so where lower-role accounts already exist, ask their holders whether XML-Sitemap appears under Settings for them, and note the answers.

Settings, filters and server rules a version match does not read

The options page as it stands today, the filters in functions.php and any Nginx rules copied into a server configuration are all outside a version match.

A match shows exposure to a known record. It cannot say whether anyone used the flaw, or whether rules once copied still match the rules the help page says should be displayed on the plugin's settings page.

A WordPress security audit tests access itself: it starts logged out and calls, without a session, the REST routes and admin-ajax actions that plugins register for logged-out visitors, and one that changes data or returns settings to an anonymous request is a finding.

Frequently asked questions

Each record has its own affected range and patched versions field. CVE-2025-64632, for one, lists all versions up to and including 4.1.22, with 4.1.23 patched. Compare your version with every range in the history, then read the update guidance at the top of it.

The records quoted on this page are ones the source data holds for the WordPress.org plugin at /plugins/google-sitemap-generator/. Its listing is headed XML Sitemap Generator for Google, and its FAQ also says Google XML Sitemap Generator. Match on that address and the version fields, whichever name a report uses.

The vendor's help page says the Sitemap Ping Protocol has been deprecated by Microsoft and Google, and that IndexNow has become the default method of notifying Microsoft Bing, Seznam.cz, Naver and Yandex. The same page also describes Notify Google and Notify Bing options, so read your own options page.

Not since version 4: the listing's FAQ says these files are dynamically generated just like any other WordPress content. Its changelog entry for 4.0 says that version will try to rename old sitemap files to end in -old.xml. Record any static sitemap file you find on the server, including one whose name ends -old.xml.

Scope the right test for your application

Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.

Data source and licence

The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.

Copyright 2012-2026 Defiant Inc.

Applies to every record listed below.

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

Copyright 1999-2026 The MITRE Corporation

Applies to every record listed below.

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.