Feed JSON Security & Risk Analysis

wordpress.org/plugins/tabletize-json-connector

Expose Wordpress posts to be used by a Tabletize data source.

10 active installs v1.0.0 PHP + WP 3.0+ Updated Unknown
feedfeedsjsonjsonptabletize
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Feed JSON Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The 'tabletize-json-connector' v1.0.0 plugin exhibits a strong security posture based on the provided static analysis and vulnerability history. The absence of any identified attack surface, dangerous functions, raw SQL queries, or external HTTP requests is a significant positive. Furthermore, the plugin appears to have no recorded vulnerability history, which suggests a mature and well-maintained codebase. The presence of prepared statements for all SQL queries also indicates good development practices for database interactions.

However, there are areas for potential improvement. The low percentage of properly escaped output (33%) raises a concern for Cross-Site Scripting (XSS) vulnerabilities, particularly if any user-supplied data is ever rendered without proper sanitization. Additionally, the complete lack of nonce checks and capability checks, while currently not posing an immediate threat due to the zero attack surface, could become a risk if new entry points are introduced in future versions without these fundamental security measures.

In conclusion, 'tabletize-json-connector' v1.0.0 is a securely developed plugin with a clean history and minimal risk. The primary area to address would be ensuring all output is properly escaped to mitigate potential XSS risks. The absence of any identified vulnerabilities or exploitable code pathways is commendable.

Key Concerns

  • Output not properly escaped
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Feed JSON Security Vulnerabilities

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

Feed JSON Code Analysis

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

Output Escaping

33% escaped3 total outputs
Attack Surface

Feed JSON Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actioninitfeed-json.php:52
actiondo_feed_jsonfeed-json.php:53
filtertemplate_includefeed-json.php:54
filterquery_varsfeed-json.php:55
Maintenance & Trust

Feed JSON Maintenance & Trust

Maintenance Signals

WordPress version tested3.9.40
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Feed JSON Developer Profile

appfactory

1 plugin · 10 total installs

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

How We Detect Feed JSON

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/tabletize-json-connector/template/feed-json.php

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Feed JSON