Relative Site URL on Content Save Security & Risk Analysis

wordpress.org/plugins/relative-site-url-on-content-save

Allows you to publish content during dev phase without having to go back and fix your content's static URLs when you switch to the production URL …

10 active installs v1.0.0 PHP + WP 2.9.2+ Updated May 16, 2010
bloginfopublishrelativeshortcodeurl
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Relative Site URL on Content Save Safe to Use in 2026?

Generally Safe

Score 85/100

Relative Site URL on Content Save has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 15yr ago
Risk Assessment

The 'relative-site-url-on-content-save' plugin v1.0.0 exhibits a strong security posture based on the provided static analysis. The code adheres to secure coding practices, demonstrated by the absence of dangerous functions, exclusive use of prepared statements for SQL, and proper output escaping. Furthermore, the lack of file operations, external HTTP requests, and a clean taint analysis report indicate a well-contained and secure codebase. The plugin also has no recorded vulnerability history, suggesting a history of stable and secure development.

However, a potential area for improvement is the reliance on capability checks and nonce checks. The absence of these checks for its single shortcode entry point, while not currently exploitable due to the lack of direct user input within the shortcode itself and no identified sensitive operations, could become a concern if the plugin's functionality evolves. The zero vulnerabilities and clean analysis are positive indicators, but the lack of built-in protection mechanisms for its entry points warrants a slight caution for future development.

Key Concerns

  • Missing capability checks for entry points
  • Missing nonce checks for entry points
Vulnerabilities
None known

Relative Site URL on Content Save Security Vulnerabilities

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

Relative Site URL on Content Save Code Analysis

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

Relative Site URL on Content Save Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[url] relative-site-url-on-content-save.php:24
WordPress Hooks 1
filtercontent_save_prerelative-site-url-on-content-save.php:19
Maintenance & Trust

Relative Site URL on Content Save Maintenance & Trust

Maintenance Signals

WordPress version tested2.9.2
Last updatedMay 16, 2010
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Relative Site URL on Content Save Developer Profile

Chris Bratlien

1 plugin · 10 total installs

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

How We Detect Relative Site URL on Content Save

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
[url]
FAQ

Frequently Asked Questions about Relative Site URL on Content Save