VSCO Workspace Contact Form 7 Integration Security & Risk Analysis

wordpress.org/plugins/tave-cf7-integration

Integrate Contact Form 7 with VSCO Workspace

200 active installs v2.0.0 PHP 7.0+ WP 4.1+ Updated Aug 14, 2025
commentscontact-form-7tave-studio-managertave
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is VSCO Workspace Contact Form 7 Integration Safe to Use in 2026?

Generally Safe

Score 100/100

VSCO Workspace Contact Form 7 Integration has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 7mo ago
Risk Assessment

The "tave-cf7-integration" v2.0.0 plugin exhibits a generally good security posture based on the provided static analysis and vulnerability history. The absence of known CVEs and common vulnerability types is a strong positive indicator. Furthermore, the static analysis reveals no critical or high-severity taint flows, a lack of dangerous functions, and no direct SQL queries executed without prepared statements. This suggests the developers have prioritized secure coding practices in these critical areas.

However, there are notable areas for improvement. The plugin has only an 8% proper output escaping rate, which is a significant concern. This means a substantial portion of its output is not being properly sanitized, potentially exposing it to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is not handled carefully. The absence of nonce checks and capability checks on entry points, although the attack surface is currently reported as zero, indicates a lack of defensive depth. If new entry points were introduced in the future without adequate security measures, these omissions could become significant risks. The single external HTTP request also warrants investigation to ensure it is not susceptible to SSRF or other network-based attacks.

In conclusion, while the plugin has a clean vulnerability history and avoids some common pitfalls like raw SQL and dangerous functions, the low output escaping rate and lack of authorization checks on potential entry points present tangible risks. Addressing the output escaping and ensuring robust authorization for any future entry points should be a priority to further enhance its security.

Key Concerns

  • Low output escaping rate
  • No nonce checks
  • No capability checks
  • External HTTP request present
Vulnerabilities
None known

VSCO Workspace Contact Form 7 Integration Security Vulnerabilities

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

VSCO Workspace Contact Form 7 Integration Code Analysis

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

Output Escaping

8% escaped12 total outputs
Attack Surface

VSCO Workspace Contact Form 7 Integration Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionadmin_menutave_cf7.php:141
actionwpcf7_before_send_mailtave_cf7.php:144
actionadmin_inittave_cf7.php:163
Maintenance & Trust

VSCO Workspace Contact Form 7 Integration Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedAug 14, 2025
PHP min version7.0
Downloads7K

Community Trust

Rating100/100
Number of ratings1
Active installs200
Developer Profile

VSCO Workspace Contact Form 7 Integration Developer Profile

vscoworkspace

2 plugins · 300 total installs

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

How We Detect VSCO Workspace Contact Form 7 Integration

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about VSCO Workspace Contact Form 7 Integration