
Full Site Title Security & Risk Analysis
wordpress.org/plugins/full-site-titleDisplays the uncut title of your site on the admin screens.
Is Full Site Title Safe to Use in 2026?
Generally Safe
Score 85/100Full Site Title has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The plugin 'full-site-title' v0.1 exhibits a very strong security posture based on the provided static analysis. There are no identified attack vectors, dangerous functions, direct SQL queries, unescaped outputs, file operations, or external HTTP requests. The complete absence of vulnerabilities in taint analysis and the zero historical CVEs further reinforce this positive assessment. This indicates that the developers have likely followed excellent security practices.
Full Site Title Security Vulnerabilities
Full Site Title Code Analysis
Full Site Title Attack Surface
WordPress Hooks 1
Maintenance & Trust
Full Site Title Maintenance & Trust
Maintenance Signals
Community Trust
Full Site Title Alternatives
Admin Slug Column
admin-slug-column
Adds a URL path column to all admin post type edit screens. Works with posts, pages, and any custom post type including WooCommerce products.
Hide Title
post-or-page-hide-title
Allows admin to hide the title tag on single pages and posts.
SubHeading
subheading
Adds the ability to easily add and display a sub title/heading on any public post type.
Change Titles Case
change-titles-case
The title transformation (converts) plugin adds administration functions to the management of posts, pages, categories and most custom content (ACF Co …
Admin Title Check
admin-title-check
Check whether the title matches other posts while adding or editing a post, page or custom post type in classic editor.
Full Site Title Developer Profile
23 plugins · 313K total installs
How We Detect Full Site Title
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
HTML / DOM Fingerprints
jQuery('#site-title').html('<?php bloginfo('name'); ?>');