XML Documents Security & Risk Analysis

wordpress.org/plugins/xml-documents

Support for managing XML documents as a custom post type and displaying them with XSLT stylesheets.

10 active installs v0.2 PHP + WP 3.1+ Updated May 31, 2011
cptcustom-post-typeteixmlxslt
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is XML Documents Safe to Use in 2026?

Generally Safe

Score 85/100

XML Documents has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 14yr ago
Risk Assessment

The "xml-documents" plugin v0.2 exhibits a mixed security posture. On the positive side, the code shows good practices by using prepared statements for all SQL queries and properly escaping 90% of its outputs. It also includes a nonce check for its single AJAX handler, which is a good step towards preventing CSRF attacks. Furthermore, there is no recorded vulnerability history, which is reassuring. However, a significant concern is the presence of an AJAX handler that lacks authentication checks. This creates a direct entry point for attackers to potentially interact with the plugin's functionality without proper authorization, posing a risk of unauthorized actions or data exposure depending on the handler's implementation.

The static analysis reveals a small attack surface with only one entry point, which is positive. The absence of taint analysis results could indicate limited complexity or that the analysis tool did not identify any flows, but it's difficult to draw firm conclusions without more detailed information. The plugin also avoids common risks such as file operations, external HTTP requests, and the use of bundled libraries. Despite the absence of known CVEs and a clean vulnerability history, the single unprotected AJAX handler represents a clear and present risk that needs to be addressed.

Key Concerns

  • Unprotected AJAX handler
Vulnerabilities
None known

XML Documents Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

XML Documents Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
1
9 escaped
Nonce Checks
1
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

90% escaped10 total outputs
Attack Surface
1 unprotected

XML Documents Attack Surface

Entry Points1
Unprotected1

AJAX Handlers 1

authwp_ajax_set-xml-documentxml-documents.php:27
WordPress Hooks 8
filterthe_contentxml-documents.php:14
filterupload_mimesxml-documents.php:17
filterwp_mime_type_iconxml-documents.php:18
actiondbx_post_advancedxml-documents.php:22
actionadmin_enqueue_scriptsxml-documents.php:25
filterattachment_fields_to_editxml-documents.php:26
filtermanage_posts_columnsxml-documents.php:30
actionmanage_posts_custom_columnxml-documents.php:31
Maintenance & Trust

XML Documents Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedMay 31, 2011
PHP min version
Downloads4K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

XML Documents Developer Profile

mitcho (Michael Yoshitaka Erlewine)

13 plugins · 6K total installs

86
trust score
Avg Security Score
88/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect XML Documents

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/xml-documents/admin.js/wp-content/plugins/xml-documents/set-xml-document.js
Script Paths
admin.jsset-xml-document.js
Version Parameters
xml-document-adminset-xml-document

HTML / DOM Fingerprints

Data Attributes
id="set-xml-document"id="wp-xml-document-class="wp-xml-document"
JS Globals
WPSetAsXMLDoc
FAQ

Frequently Asked Questions about XML Documents