wpuntexturize Security & Risk Analysis

wordpress.org/plugins/wpuntexturize

Prevent WordPress from converting single and double quotation marks into their curly alternatives.

900 active installs v2.3 PHP + WP 5.5+ Updated Apr 8, 2025
formattingpostquotessubstitutionswptexturize
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is wpuntexturize Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The WP Untexturize plugin version 2.3 exhibits a strong security posture based on the provided static analysis and vulnerability history. The code analysis reveals no dangerous functions, file operations, external HTTP requests, or SQL queries that are not properly prepared. All identified outputs are correctly escaped, and there are no taint flows with unsanitized paths. This indicates that the developers have followed good security practices in its implementation, minimizing common attack vectors.

Furthermore, the plugin has no recorded vulnerabilities, including CVEs, which is a significant positive indicator. The absence of historical issues suggests a history of stable and secure development. The code analysis also shows a minimal attack surface with no AJAX handlers, REST API routes, shortcodes, or cron events that are exposed without authentication or proper checks. The presence of a capability check further enhances its security by ensuring that the functionality is accessible only to authorized users.

While the plugin demonstrates excellent security practices and a clean vulnerability history, the complete absence of certain security checks like nonce checks on its (hypothetical) entry points could be a minor area for consideration if the attack surface were larger. However, given that the attack surface is reported as zero, this is not a practical concern for this specific version. Overall, WP Untexturize v2.3 appears to be a highly secure plugin.

Vulnerabilities
None known

wpuntexturize Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

wpuntexturize Release Timeline

v2.3Current
v2.2.2
v2.2.1
v2.2
v2.1
v2.0
v1.7.1
v1.7
v1.6.3
v1.6.2
v1.6.1
v1.5.4
v1.5.3
v1.5.2
v1.5.1
v1.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
Code Analysis
Analyzed Mar 16, 2026

wpuntexturize Code Analysis

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

Output Escaping

100% escaped4 total outputs
Attack Surface

wpuntexturize Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionadmin_initwpuntexturize.php:74
filterallowed_optionswpuntexturize.php:152
filterplugin_action_links_wpuntexturize/wpuntexturize.phpwpuntexturize.php:162
actionplugins_loadedwpuntexturize.php:265
filterc2c_wpuntexturizewpuntexturize.php:288
Maintenance & Trust

wpuntexturize Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedApr 8, 2025
PHP min version
Downloads26K

Community Trust

Rating92/100
Number of ratings12
Active installs900
Developer Profile

wpuntexturize Developer Profile

Scott Reilly

63 plugins · 92K total installs

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

How We Detect wpuntexturize

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wpuntexturize/wpuntexturize.js/wp-content/plugins/wpuntexturize/wpuntexturize.css
Script Paths
/wp-content/plugins/wpuntexturize/wpuntexturize.js

HTML / DOM Fingerprints

Data Attributes
id="wpuntexturize"name="c2c_wpuntexturize"for="c2c_wpuntexturize"
JS Globals
c2c_wpuntexturizewpuntexturize_filters
FAQ

Frequently Asked Questions about wpuntexturize