magento2-security-scan

Solid

This skill should be used when the user asks to "run a security audit", "find vulnerabilities", "check for XSS", "check CSRF protection", "validate form security", "run a dependency audit", "check for outdated packages", "run a PCI compliance check", or "do a security review before deploy". Scans Magento 2 code for security vulnerabilities and compliance issues. DEPENDENT on magento2-dev-core for security patterns.

AI & Automation 4 stars 2 forks Updated today MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Magento 2 Security Scanner This skill performs security scanning for vulnerabilities, misconfigurations, and compliance issues. ## Related Skills **REQUIRED BACKGROUND:** Load `magento2-dev-core` first — this skill scans for violations of the security patterns it defines (escaping, discouraged functions, ObjectManager misuse), and its patterns are what you fix findings with. Part of the QA trio with `magento2-linter` (style/static analysis) and `magento2-performance-audit` (runtime/infrastructure). Re-check API/resolver-specific findings against `magento2-backend-dev`. ## Vulnerability Categories ### 1. Injection Vulnerabilities | Type | Pattern | Severity | Code | |------|---------|----------|------| | SQL Injection | Direct SQL with user input | Critical | M2-SEC-001 | | XSS (Reflected) | Unescaped user input in output | High | M2-SEC-003 | | XSS (Stored) | Unescaped database content | Critical | M2-SEC-002 | | Command Injection | System command execution with user input | Critical | M2-SEC-004 | Full scale and code catalogue: `magento2-dev-core/references/severity-and-codes.md`. ### 2. Authentication & Authorization | Check | Command | |-------|---------| | Admin path changed | Check env.php for custom admin path | | 2FA enabled | Check admin/twofactor module | | Password hashing | Verify EncryptorInterface usage | | Session security | Check cookie configuration | ### 3. Data Exposure ```bash # Check for exposed sensitive files curl -I https://store.test/app/...

Details

Author
ddtcorex
Repository
ddtcorex/dev-skills-hub
Created
3 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

security-scan

Runs a repository or path security scan and produces a severity-ranked report covering hardcoded secrets and credential patterns, dependency CVEs via npm audit and equivalents, OWASP code patterns such as SQL injection, XSS, SSRF, path traversal and insecure deserialization, unsafe file permissions, and missing HTTP security headers. Use when a scan, audit, or vulnerability check is actually being asked for — /security-scan, scan for vulnerabilities, security audit, check for leaked secrets — or before shipping new code that adds authentication, cryptography, input handling, SQL, or file uploads. Reading, explaining, or editing code that merely happens to touch auth or SQL does not warrant it, since it emits a full scan report rather than an inline observation.

7 Updated 4 weeks ago
pfangueiro
Code & Development Solid

magento2-linter

This skill should be used when the user asks to "check coding standards", "run phpcs", "lint my code", "run PHPStan analysis", "run static analysis on this module", "find security issues in code", "check code complexity", "find code smells", "detect unused code", "audit custom code", or "verify code quality before commit". Runs automated code quality checks for Magento 2 projects — PHPCS (Magento2 standard), PHPStan, and PHPMD. DEPENDENT on magento2-dev-core for understanding the coding standards it validates.

4 Updated today
ddtcorex
API & Backend Solid

magento2-performance-audit

This skill should be used when the user asks to "audit performance", "check Core Web Vitals", "run Lighthouse", "check server configuration", "verify Redis/Varnish setup", "analyze database queries", "find N+1 query issues", "review indexer configuration", "check cron health", "debug cache flush", asks "why does full_page cache keep flushing", wants to "trace FPC invalidation", or reports "too many ajax requests", a "customer data section reload storm", or a "crawler overloading server". Performs a comprehensive performance and health audit for Magento 2 projects against Adobe Commerce Best Practices. DEPENDENT on magento2-dev-core for code-level performance patterns.

4 Updated today
ddtcorex