Bloom for Publishers Security & Risk Analysis

wordpress.org/plugins/bloom-for-publishers

Geotag your posts to enable local search and other hyperlocal experiences for your readers.

90 active installs v1.7.10 PHP 5.6+ WP 5.2+ Updated Feb 23, 2026
geotaglocal-newslocal-searchmappingpersonalization
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Bloom for Publishers Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The plugin 'bloom-for-publishers' v1.7.10 exhibits a strong security posture based on the provided static analysis. The absence of dangerous functions, 100% proper output escaping, and the exclusive use of prepared statements for SQL queries are significant strengths. The plugin also demonstrates good practice by employing nonce checks, although capability checks are notably absent. The limited attack surface, with only one shortcode and no unprotected entry points, further contributes to its secure design. The vulnerability history is also clean, with no recorded CVEs, suggesting a history of robust security maintenance.

While the static analysis reveals no immediate critical vulnerabilities, the lack of capability checks on the shortcode represents a potential area for concern. If the shortcode's functionality relies on user permissions, its absence could lead to unauthorized access or actions by users who should not have such privileges. However, given the overall excellent security metrics and the lack of any historical vulnerabilities or critical taint flows, the immediate risk appears low. The plugin is well-developed from a security perspective, but a deeper review of the shortcode's implementation is recommended to ensure it properly handles authorization.

Key Concerns

  • Missing capability checks on shortcode
Vulnerabilities
None known

Bloom for Publishers Security Vulnerabilities

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

Bloom for Publishers Code Analysis

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

SQL Query Safety

100% prepared2 total queries

Output Escaping

100% escaped157 total outputs
Attack Surface

Bloom for Publishers Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[bloom] post\post.php:12
WordPress Hooks 22
actionadmin_noticesadmin\admin-post.php:3
actionadd_meta_boxesadmin\admin-post.php:4
actionfuture_to_publishadmin\admin-post.php:5
actionpost_updatedadmin\admin-post.php:6
actionadmin_enqueue_scriptsadmin\admin-post.php:97
actionadmin_menuadmin\admin-settings.php:8
actionadmin_initadmin\admin-settings.php:11
actionadmin_enqueue_scriptsadmin\admin-settings.php:14
actionadmin_noticesadmin\admin-settings.php:17
actionmanage_posts_custom_columnadmin\admin-settings.php:20
filtermanage_post_posts_columnsadmin\admin-settings.php:21
actionwp_headpost\post.php:3
actionamp_post_template_datapost\post.php:6
actionamp_post_template_csspost\post.php:7
actionwp_enqueue_scriptspost\post.php:9
filterthe_contentpost\post.php:13
filterthe_contentpost\post.php:14
actioninitsearch\search.php:7
actionwp_footersearch\search.php:8
actionamp_post_template_datasearch\search.php:10
actionamp_post_template_csssearch\search.php:11
actionwp_enqueue_scriptssearch\search.php:13
Maintenance & Trust

Bloom for Publishers Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 23, 2026
PHP min version5.6
Downloads23K

Community Trust

Rating0/100
Number of ratings0
Active installs90
Developer Profile

Bloom for Publishers Developer Profile

bloomfornews

1 plugin · 90 total installs

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

How We Detect Bloom for Publishers

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bloom-for-publishers/css/admin-post.css/wp-content/plugins/bloom-for-publishers/css/global.css/wp-content/plugins/bloom-for-publishers/js/admin-post.js/wp-content/plugins/bloom-for-publishers/js/geocode.js
Script Paths
https://maps.googleapis.com/maps/api/js?language=en&key=
Version Parameters
bloom-for-publishers/css/admin-post.css?ver=bloom-for-publishers/css/global.css?ver=bloom-for-publishers/js/admin-post.js?ver=bloom-for-publishers/js/geocode.js?ver=

HTML / DOM Fingerprints

CSS Classes
blm_location_form
HTML Comments
Admin Post: admin-post.phpNote: In block editor (Gutenberg), this doesn't show by defaultNote cont. A redundant message is displayed in the Post Location section
Data Attributes
data-code
FAQ

Frequently Asked Questions about Bloom for Publishers