Portfolio CPT Security & Risk Analysis

wordpress.org/plugins/portfolio-cpt

Enables a 'Portfolio' type and 'Portfolio Tags' taxonomy.

300 active installs v1.0.0 PHP 5.2+ WP 4.0+ Updated Aug 30, 2018
art-portfoliocustom-post-typephotography-portfolioportfolioprojects
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Portfolio CPT Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The "portfolio-cpt" plugin v1.0.0 exhibits a strong security posture based on the provided static analysis. The absence of dangerous functions, proper use of prepared statements for all SQL queries, and 100% properly escaped output are significant strengths. Furthermore, the presence of a nonce check and a complete lack of known vulnerabilities in its history indicate diligent development practices. The limited attack surface, with only one shortcode and no unprotected entry points, further contributes to its good security standing.

While the analysis reveals no critical or high-severity issues in taint flows, and no unpatched vulnerabilities, the absence of capability checks on any entry points (even though there are no unprotected ones currently) is a potential concern. If future updates introduce new entry points or modify existing ones, the lack of explicit capability checks could inadvertently expose functionality to unauthorized users.

In conclusion, "portfolio-cpt" v1.0.0 is a well-secured plugin with a commendable track record and robust coding practices. The primary area for improvement lies in implementing capability checks as a proactive security measure for all functionalities, ensuring long-term resilience against potential future threats.

Key Concerns

  • No capability checks found on entry points
Vulnerabilities
None known

Portfolio CPT Security Vulnerabilities

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

Portfolio CPT Code Analysis

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

Output Escaping

100% escaped6 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
settings_save (includes\class-portfolio-cpt-permalink.php:52)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Portfolio CPT Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[portfolio] includes\register-shortcode.php:11
WordPress Hooks 5
filteradmin_initincludes\class-portfolio-cpt-permalink.php:29
actioninitincludes\register-cpt.php:59
actioninitincludes\register-taxonomy.php:47
actionplugins_loadedportfolio-cpt.php:32
actionwp_enqueue_scriptsportfolio-cpt.php:33
Maintenance & Trust

Portfolio CPT Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedAug 30, 2018
PHP min version5.2
Downloads5K

Community Trust

Rating0/100
Number of ratings0
Active installs300
Developer Profile

Portfolio CPT Developer Profile

DannyCooper

9 plugins · 5K total installs

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

How We Detect Portfolio CPT

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/portfolio-cpt/assets/css/style.css

HTML / DOM Fingerprints

CSS Classes
portfolioportfolio-itemsportfolio-itemportfolio-item__imageportfolio-item__detailsportfolio-item__nameportfolio-item__tags
Data Attributes
data-post-id
Shortcode Output
<div class="portfolio style- columns-portfolio-itemsportfolio-item
FAQ

Frequently Asked Questions about Portfolio CPT