Leaderboard github.com
fossasia/loklak_wp_plugins
AI provenance
0%
none-detected
- Confidence
- 56%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
46/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
74/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% none-detected
No AI attribution or AI-consistent velocity signals detected.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)0.92
Lines added per month all AI-attributed share
- 2015-06344,511 · 0% AI
- 2015-075,758 · 0% AI
- 2015-0833,882 · 0% AI
- 2015-09413 · 0% AI
- 2016-0147,150 · 0% AI
- 2016-02534 · 0% AI
- 2016-0417,149 · 0% AI
- 2016-05224 · 0% AI
- 2016-06802 · 0% AI
- 2016-07184,154 · 0% AI
- 2016-087,932 · 0% AI
- 2016-1179 · 0% AI
- 2016-1252 · 0% AI
- 2017-030 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 65
- effective_loc
- 642,640
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 543,464
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 1,896
- measured_loc
- 21,377
- median_loc_per_hour
- 192.88
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 15,526
- pre_ai_era_bursts
- 3
- pre_ai_era_measured_loc
- 21,377
- work_units
- 29
Release velocityskipped
Coding styleok8 items
- step-by-step narration comment: // Next, Plugins
- step-by-step narration comment: // Next, those themes we all love
- step-by-step narration comment: // Next, Process any core update
- step-by-step narration comment: // Finally, Process any new translations
- step-by-step narration comment: // Next, Plugins
- step-by-step narration comment: // Next, those themes we all love
- step-by-step narration comment: // Next, Process any core update
- step-by-step narration comment: // Finally, Process any new translations
- count:assistant_voice
- 2
- count:emoji_in_code
- 0
- count:narrated_steps
- 511
- count:placeholder
- 0
- files:assistant_voice
- 1
- files:emoji_in_code
- 0
- files:narrated_steps
- 171
- files:placeholder
- 0
- index
- 0.92
- lines_scanned
- 557,386
- per_kloc:assistant_voice
- 0.00
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0.92
- per_kloc:placeholder
- 0
Code quality
46 poor
Code quality is poor: test-to-source ratio 0.07, no CI test run detected; 31% of function code in complex or long functions; 27% duplicated lines. Weakest area: duplication.
How the score is built
- Complexity40
- Duplication20
- Lint and smells98
- Tests and CI29
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- SimplePie_Item::get_enclosures in wp-includes/SimplePie/Item.php: complexity 356, 1676 lines
- getid3_id3v2::ParseID3v2Frame in wp-includes/ID3/module.tag.id3v2.php: complexity 352, 1098 lines
- getid3_quicktime::QuicktimeParseAtom in wp-includes/ID3/module.audio-video.quicktime.php: complexity 347, 1050 lines
- WP_Query::get_posts in wp-includes/query.php: complexity 285, 759 lines
- rotating_tweets_display in wp-content/plugins/wp-rotatingtweets/rotatingtweets.php: complexity 269, 674 lines
- getid3_riff::Analyze in wp-includes/ID3/module.audio-video.riff.php: complexity 228, 995 lines
- redirect_canonical in wp-includes/canonical.php: complexity 217, 363 lines
- getid3_matroska::parseEBML in wp-includes/ID3/module.audio-video.matroska.php: complexity 190, 544 lines
- getid3_asf::Analyze in wp-includes/ID3/module.audio-video.asf.php: complexity 189, 909 lines
- map_meta_cap in wp-includes/capabilities.php: complexity 122, 293 lines
- complex_functions
- 673
- function_nloc
- 272,445
- functions
- 17,396
- long_functions
- 239
- many_param_functions
- 5
- mean_ccn
- 4.09
- p90_ccn
- 9
- risky_nloc_share
- 30.8%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: wp-admin/admin-header.php:74 and wp-admin/includes/template.php:1587
- 6+ duplicated lines: wp-admin/admin-post.php:12 and wp-admin/async-upload.php:13
- 6+ duplicated lines: wp-admin/class-wp-upgrader.php:37 and wp-admin/includes/class-wp-upgrader.php:38
- 6+ duplicated lines: wp-admin/class-wp-upgrader.php:669 and wp-admin/class-wp-upgrader.php:1107
- 6+ duplicated lines: wp-admin/comment.php:171 and wp-admin/edit-form-comment.php:109
- 6+ duplicated lines: wp-admin/credits.php:15 and wp-admin/freedoms.php:14
- 6+ duplicated lines: wp-admin/custom-background.php:35 and wp-admin/custom-header.php:44
- 6+ duplicated lines: wp-admin/custom-header.php:1156 and wp-admin/includes/class-wp-site-icon.php:90
- 6+ duplicated lines: wp-admin/custom-header.php:1264 and wp-admin/custom-header.php:1290
- 6+ duplicated lines: wp-admin/edit-form-advanced.php:406 and wp-admin/media.php:76
- compared_lines
- 361,017
- duplicated_lines
- 97,665
- duplicated_share
- 27.1%
- files
- 2,190
Lintok
- category:best-practice
- 36
- category:correctness
- 37
- findings
- 73
- scanned_lines
- 557,386
- weighted_findings
- 46
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 0
- cochange_commits
- 43
- cochange_share
- 14.0%
- source_lines
- 557,386
- test_lines
- 39,960
- test_ratio
- 0.07
Documentationok2 items
- Readme.md
Readme.md - license.txt
license.txt
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 43
Type safetyskipped
Security
74 adequate
Security posture is adequate: 423 high-severity SAST findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)53
- Vulnerable dependencies100
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 1
- declared
- 1
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 2,210
- findings_high
- 423
- findings_low
- 2
- findings_medium
- 1,785
- parse_errors
- 14
- scanned_lines
- 557,386
- weighted_findings
- 1,018.08
Dependencies (osv-scanner)ok
- penalty
- 0
- vulnerabilities
- 0
- vulnerable_packages
- 0
- vulns_critical
- 0
- vulns_high
- 0
- vulns_low
- 0
- vulns_medium
- 0
- vulns_unknown
- 0
CI workflows (zizmor)skipped
Security postureok20 items
- wp-content/plugins/amazon-s3-and-cloudfront/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/amazon-s3-and-cloudfront/composer.json - wp-content/plugins/amazon-web-services/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/amazon-web-services/composer.json - wp-content/plugins/tweet-feed-widget/loklak_php_api/Requests/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/tweet-feed-widget/loklak_php_api/Requests/composer.json - wp-content/plugins/tweet-feed-widget/loklak_php_api/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/tweet-feed-widget/loklak_php_api/composer.json - wp-content/plugins/tweet-feed-widget/loklak_php_api/package.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/tweet-feed-widget/loklak_php_api/package.json - wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/Requests/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/Requests/composer.json - wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/composer.json - wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/package.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/package.json - wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/Requests/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/Requests/composer.json - wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/composer.json - wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/package.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/package.json - wp-content/plugins/wp-dev-buddy/loklak_php_api/Requests/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-dev-buddy/loklak_php_api/Requests/composer.json - wp-content/plugins/wp-dev-buddy/loklak_php_api/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-dev-buddy/loklak_php_api/composer.json - wp-content/plugins/wp-dev-buddy/loklak_php_api/package.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-dev-buddy/loklak_php_api/package.json - wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/Requests/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/Requests/composer.json - wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/composer.json - wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/package.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/package.json - wp-content/plugins/wp-recent-tweet/loklak_php_api/Requests/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-recent-tweet/loklak_php_api/Requests/composer.json - wp-content/plugins/wp-recent-tweet/loklak_php_api/composer.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-recent-tweet/loklak_php_api/composer.json - wp-content/plugins/wp-recent-tweet/loklak_php_api/package.json has no lockfile alongside it (unpinned dependencies)
wp-content/plugins/wp-recent-tweet/loklak_php_api/package.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 42
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
300 high37 medium36 low
373 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| high | opengrep/php.lang.security.injection.echoed-request |
wp-activate.php:106 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-activate.php:115 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-activate.php:116 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.file-inclusion |
wp-admin/admin.php:262 | Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead,... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.file-inclusion |
wp-admin/admin.php:264 | Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead,... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/async-upload.php:102 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/async-upload.php:117 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/async-upload.php:62 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/async-upload.php:63 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/async-upload.php:72 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/async-upload.php:76 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/comment.php:179 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/comment.php:205 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/comment.php:207 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/comment.php:216 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/comment.php:250 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/comment.php:309 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/custom-header.php:808 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/custom-header.php:808 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/custom-header.php:808 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/edit-comments.php:276 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/edit-form-advanced.php:485 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/edit-tags.php:109 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/edit-tags.php:169 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/edit.php:329 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:1214 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:1465 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:1500 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:155 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:1927 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:2050 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:2072 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:2127 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:2231 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:2269 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:2406 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:2484 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:2530 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:3015 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:3041 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:539 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:581 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:607 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ajax-actions.php:629 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ajax-actions.php:910 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:100 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:180 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:196 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:209 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:239 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:240 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:302 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:317 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:319 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:325 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:335 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:362 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:364 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:407 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:417 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:471 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:559 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:562 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:563 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:605 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:73 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:75 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.ftp-use |
wp-admin/includes/class-wp-filesystem-ftpext.php:98 | FTP allows for unencrypted file transfers. Consider using an encrypted alternative. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/class-wp-ms-themes-list-table.php:357 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/class-wp-plugins-list-table.php:687 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/class-wp-press-this.php:109 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/dashboard.php:1052 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/dashboard.php:1394 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/dashboard.php:971 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/file.php:1204 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/file.php:1240 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/file.php:531 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/image.php:144 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:1770 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:1902 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2002 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2004 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2066 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2067 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2229 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2241 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2246 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2378 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2429 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2447 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2490 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/media.php:2513 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/media.php:3127 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/media.php:3129 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ms.php:1035 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/includes/ms.php:1053 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ms.php:1068 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ms.php:1070 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/ms.php:1072 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/ms.php:268 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/ms.php:349 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:416 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:444 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:459 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:533 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:538 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:675 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:685 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:691 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:696 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/nav-menu.php:724 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/plugin-install.php:194 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:507 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:511 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:519 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:537 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:547 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:549 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:557 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:563 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:567 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:569 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:571 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:594 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:594 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:597 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:599 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:617 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:619 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:625 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:646 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:658 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:663 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/includes/plugin-install.php:667 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/plugin.php:1092 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/schema.php:1094 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.md5-loose-equality |
wp-admin/includes/update-core.php:964 | Make sure comparisons involving md5 values are strict (use `===` not `==`) to avoid type juggling issues [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/includes/upgrade.php:666 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/install.php:385 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
wp-admin/js/nav-menu.js:1090 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
wp-admin/js/nav-menu.js:1090 | User controlled data in a `wrap.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
wp-admin/js/press-this.js:83 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
wp-admin/js/press-this.js:83 | User controlled data in a `textarea.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/link.php:79 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/link.php:88 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/load-scripts.php:69 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/load-styles.php:91 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/media-new.php:75 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/media-new.php:77 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/media.php:120 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/media.php:121 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-document-method |
wp-admin/nav-menu.js:1074 | User controlled data in methods like `innerHTML`, `outerHTML` or `document.write` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/javascript.browser.security.insecure-innerhtml |
wp-admin/nav-menu.js:1074 | User controlled data in a `wrap.innerHTML` is an anti-pattern that can lead to XSS vulnerabilities [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/nav-menus.php:338 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/nav-menus.php:345 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/nav-menus.php:699 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/nav-menus.php:736 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/nav-menus.php:872 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/nav-menus.php:931 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/nav-menus.php:931 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-info.php:145 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-info.php:145 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-info.php:156 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-info.php:176 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-info.php:183 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-new.php:191 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-settings.php:108 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/network/site-settings.php:123 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-settings.php:148 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-settings.php:149 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-settings.php:97 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-settings.php:97 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-themes.php:151 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-themes.php:151 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-themes.php:162 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-themes.php:174 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-themes.php:182 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-users.php:200 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-users.php:206 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-users.php:206 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/site-users.php:217 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/sites.php:109 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/sites.php:298 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/themes.php:146 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/themes.php:261 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/themes.php:269 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/themes.php:277 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/network/themes.php:91 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/themes.php:94 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/upgrade.php:100 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/upgrade.php:104 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/network/upgrade.php:58 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/user-new.php:105 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/network/user-new.php:98 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugin-editor.php:181 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugin-editor.php:260 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/plugins.php:140 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugins.php:143 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugins.php:306 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/plugins.php:306 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugins.php:310 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugins.php:434 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/plugins.php:443 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/post.php:178 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/post.php:191 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/post.php:246 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/post.php:270 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/setup-config.php:174 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/setup-config.php:367 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/setup-config.php:399 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/themes.php:37 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/update-core.php:293 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/update-core.php:364 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update-core.php:663 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/update-core.php:671 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update-core.php:691 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/update-core.php:700 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update-core.php:735 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:130 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:185 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:206 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:238 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:287 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:37 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:62 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:75 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/update.php:77 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.file-inclusion |
wp-admin/update.php:90 | Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead,... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/upgrade.php:111 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/upload.php:309 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/user-new.php:291 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/user-new.php:298 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-admin/user-new.php:73 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/users.php:160 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/users.php:252 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/users.php:255 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/users.php:382 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/users.php:385 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/users.php:388 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/users.php:479 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/widgets.php:127 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/widgets.php:268 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/widgets.php:285 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/widgets.php:303 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-admin/widgets.php:324 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/widgets.php:367 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-admin/widgets.php:370 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.eval-use |
wp-content/pg4wp/core.php:32 | Evaluating non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-content/plugins/akismet/class.akismet-admin.php:367 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.printed-request |
wp-content/plugins/akismet/class.akismet-admin.php:442 | `Printing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.printed-request |
wp-content/plugins/akismet/class.akismet-admin.php:454 | `Printing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/amazon-s3-and-cloudfront/classes/as3cf-notices.php:96 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/cloudinary.php:72 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/cloudinary_api.php:220 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/cloudinary_api.php:238 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/cloudinary_api.php:272 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/tweet-feed-widget/lib/wp-twitter.php:214 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/tweet-feed-widget/lib/wp-twitter.php:49 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/tweet-feed-widget/lib/wp-twitter.php:63 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/tweet-feed-widget/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/tweet-feed-widget/tlc-transients.php:14 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/tweet-feed-widget/tlc-transients.php:44 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/tweet-feed-widget/wp-twitter-widget.php:1113 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.tainted-sql-string |
wp-content/plugins/user-role-editor/includes/classes/ure-lib.php:2143 | User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL... | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-content/plugins/wordpress-https/admin/js/metabox.php:24 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Settings.php:155 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-accesspress-twitter-feed/APTF.class.php:87 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-accesspress-twitter-feed/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-accesspress-twitter-feed/oauth/OAuth.php:479 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-accesspress-twitter-feed/twitteroauth/OAuth.php:492 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-ai-twitter-feeds/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-ai-twitter-feeds/twitteroauth/OAuth.php:479 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-dev-buddy/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-juiz-last-tweet-widget/inc/OAuth.php:476 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-juiz-last-tweet-widget/inc/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-recent-tweet/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-recent-tweet/twitteroauth.php:486 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-rotatingtweets/lib/WP_OAuth.php:481 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-rotatingtweets/lib/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-rotatingtweets/rotatingtweets.php:108 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-rotatingtweets/rotatingtweets.php:627 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-simple-twitter-feeds/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-simple-twitter-feeds/twitteroauth/OAuth.php:479 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-content/plugins/wp-tweeple/inc/class-tweeple-admin.php:124 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-tweeple/lib/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-tweeple/lib/tmhOAuth/tmhOAuth.php:128 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
wp-content/plugins/wp-tweeple/lib/tmhOAuth/tmhUtilities.php:260 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.extract-user-data |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lib/twitter-api-admin.php:127 | Do not call 'extract()' on user-controllable data. If you must, then you must also provide the EXTR_SKIP flag to prevent overwriting existing variables. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.extract-user-data |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lib/twitter-api-admin.php:141 | Do not call 'extract()' on user-controllable data. If you must, then you must also provide the EXTR_SKIP flag to prevent overwriting existing variables. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lib/twitter-api-core.php:254 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lib/twitter-api-core.php:63 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lib/twitter-api-core.php:81 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-tweets-widget/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-tweetscroll-widget/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-tweetscroll-widget/twitter/OAuth.php:479 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-content/plugins/wp-tweetscroll-widget/widget-tweetscroll.php:508 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.injection.echoed-request |
wp-content/plugins/wp-tweetscroll-widget/widget-tweetscroll.php:532 | `Echo`ing user input risks cross-site scripting vulnerability. You should use `htmlentities()` when showing data to users. [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.curl-ssl-verifypeer-off |
wp-content/plugins/wp-twidget/lib/loklak_php_api/Requests/library/Requests/Transport/cURL.php:151 | SSL verification is disabled but should not be (currently CURLOPT_SSL_VERIFYPEER= 0) [confidence medium] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.weak-crypto |
wp-content/plugins/wp-twidget/lib/tmhOAuth.php:133 | Detected usage of weak crypto function. Consider using stronger alternatives. [confidence low] | Static analysis (opengrep) |
| high | opengrep/php.lang.security.exec-use |
wp-content/plugins/wp-twidget/lib/tmhUtilities.php:260 | Executing non-constant commands. This can lead to command injection. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-admin/js/common.js:101 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-admin/js/common.js:93 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-admin/js/image-edit.js:486 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-admin/js/post.js:86 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-admin/js/set-post-thumbnail.js:14 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-admin/js/theme.js:1780 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-admin/js/theme.js:718 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/amazon-s3-and-cloudfront/assets/js/notice.js:20 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/amazon-s3-and-cloudfront/assets/js/script.js:614 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/amazon-s3-and-cloudfront/assets/js/script.js:620 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/cloudinary.js:23 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/cloudinary.js:63 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.form.js:298 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-js.js:102 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-js.js:106 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-js.js:110 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-content/plugins/user-role-editor/js/ure-js.js:200 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-js.js:242 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-js.js:246 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-content/plugins/user-role-editor/js/ure-js.js:287 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-content/plugins/user-role-editor/js/ure-js.js:363 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-users.js:52 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-users.js:71 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-users.js:73 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-users.js:76 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-content/plugins/user-role-editor/js/ure-users.js:80 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-content/plugins/wp-tweeple/assets/js/admin.js:27 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-content/plugins/wp-tweeple/assets/js/admin.js:83 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-includes/js/colorpicker.js:542 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-includes/js/colorpicker.js:552 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
wp-includes/js/customize-loader.js:204 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
wp-includes/js/customize-selective-refresh.js:597 | JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-prompt |
wp-includes/js/quicktags.js:631 | found prompt() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-prompt |
wp-includes/js/quicktags.js:654 | found prompt() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-prompt |
wp-includes/js/quicktags.js:656 | found prompt() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
wp-includes/js/swfupload/swfupload.js:978 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.lazy-load-module |
wp-includes/js/tinymce/plugins/paste/plugin.js:41 | Lazy loading can complicate code bundling if care is not taken, also `require`s are run synchronously by Node.js. If they are called from within a function, it may block other requests from being handled at a more critical time. The... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
web_boot.sh:2 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-admin/js/press-this.js:136 | `textEditor.style.height` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:473 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:474 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:475 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:476 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:477 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:478 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:512 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:513 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:514 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:515 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:516 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:517 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:551 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:552 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:553 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:554 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:555 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:556 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:590 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:591 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:592 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:593 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:594 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:595 | `points[points.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/plugins/cloudinary-image-management-and-manipulation-in-the-cloud-cdn/js/jquery.bt.js:619 | `newPoints[newPoints.length]` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lang/merge.sh:8 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
wp-content/plugins/wp-tweets-widget/api/wp-twitter-api/lang/update.sh:8 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/themes/twentyeleven/js/html5.js:4 | `b` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/themes/twentyfifteen/js/html5.js:5 | `b` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/themes/twentyfourteen/js/html5.js:4 | `b` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-content/themes/twentythirteen/js/html5.js:4 | `b` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-includes/js/media-views.js:7715 | `disabled` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-includes/js/swfupload/swfupload.js:319 | `movieElement` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
wp-includes/js/tinymce/utils/mctabs.js:23 | `value` is assigned twice; the first assignment is useless | Lint |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 73 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 300 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | c86b3fd810b3 | prov-5+qual-2+sec-2 | 0% | 46 | 74 |
| 2026-11-14 | c86b3fd810b3 | prov-4+qual-2+sec-2 | 0% | 46 | 74 |
Full text report
- Repository: https://github.com/fossasia/loklak_wp_plugins
- Commit:
c86b3fd810b328c4c6d68eeb8a400f90c0f50dd2 - Generated: 2026-11-14T14:52:04+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | none-detected | 56% | 100% |
| Code quality | 46 | poor | 90% | 100% |
| Security | 74 | adequate | 85% | 100% |
AI provenance
No AI attribution or AI-consistent velocity signals detected.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
Stylometry index: 0.92 per 1,000 lines (narrated steps 511, placeholders 0, assistant phrasing 2, emoji 0). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2015-07 | 5,758 | 0% |
| 2015-08 | 33,882 | 0% |
| 2015-09 | 413 | 0% |
| 2016-01 | 47,150 | 0% |
| 2016-02 | 534 | 0% |
| 2016-04 | 17,149 | 0% |
| 2016-05 | 224 | 0% |
| 2016-06 | 802 | 0% |
| 2016-07 | 184,154 | 0% |
| 2016-08 | 7,932 | 0% |
| 2016-11 | 79 | 0% |
| 2016-12 | 52 | 0% |
Evidence
- step-by-step narration comment: // Next, Plugins (wp-admin/cla)
- step-by-step narration comment: // Next, those themes we all love (wp-admin/cla)
- step-by-step narration comment: // Next, Process any core update (wp-admin/cla)
- step-by-step narration comment: // Finally, Process any new translations (wp-admin/cla)
- step-by-step narration comment: // Next, Plugins (wp-admin/inc)
- step-by-step narration comment: // Next, those themes we all love (wp-admin/inc)
- step-by-step narration comment: // Next, Process any core update (wp-admin/inc)
- step-by-step narration comment: // Finally, Process any new translations (wp-admin/inc)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is poor: test-to-source ratio 0.07, no CI test run detected; 31% of function code in complex or long functions; 27% duplicated lines. Weakest area: duplication.
| Area | Score |
|---|---|
| Complexity (lizard) | 40 |
| Duplication | 20 |
| Code smells (Opengrep) | 98 |
| Tests and CI | 29 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 17,396; mean complexity 4.1, 90th percentile 9; 673 complex and 239 long functions
- Duplicated lines: 27.1% of 361,017 compared
- Tests: 39,960 test lines for 557,386 source lines (ratio 0.07); CI test commands: none detected; 14% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- SimplePie_Item::get_enclosures in wp-includes/SimplePie/Item.php: complexity 356, 1676 lines
- getid3_id3v2::ParseID3v2Frame in wp-includes/ID3/module.tag.id3v2.php: complexity 352, 1098 lines
- getid3_quicktime::QuicktimeParseAtom in wp-includes/ID3/module.audio-video.quicktime.php: complexity 347, 1050 lines
- WP_Query::get_posts in wp-includes/query.php: complexity 285, 759 lines
- rotating_tweets_display in wp-content/plugins/wp-rotatingtweets/rotatingtweets.php: complexity 269, 674 lines
Security
Security posture is adequate: 423 high-severity SAST findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 53 |
| Vulnerable dependencies (OSV) | 100 |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-activate.php:106 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-activate.php:115 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-activate.php:116 |
| high | opengrep/php.lang.security.file-inclusion: Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead, explicitly specify what to include. If that is not a viable solution, [confidence low] |
wp-admin/admin.php:262 |
| high | opengrep/php.lang.security.file-inclusion: Detected non-constant file inclusion. This can lead to local file inclusion (LFI) or remote file inclusion (RFI) if user input reaches this statement. LFI and RFI could lead to sensitive files being obtained by attackers. Instead, explicitly specify what to include. If that is not a viable solution, [confidence low] |
wp-admin/admin.php:264 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/async-upload.php:62 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/async-upload.php:63 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/async-upload.php:72 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/async-upload.php:76 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/async-upload.php:102 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/async-upload.php:117 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/comment.php:179 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/comment.php:205 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/comment.php:207 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/comment.php:216 |
| high | opengrep/php.lang.security.injection.tainted-sql-string: User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL injection, which could let an attacker steal or manipulate data [confidence medium] |
wp-admin/comment.php:250 |
| high | opengrep/php.lang.security.injection.tainted-sql-string: User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL injection, which could let an attacker steal or manipulate data [confidence medium] |
wp-admin/comment.php:309 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/custom-header.php:808 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/custom-header.php:808 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/custom-header.php:808 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/edit-comments.php:276 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/edit-form-advanced.php:485 |
| high | opengrep/php.lang.security.injection.tainted-sql-string: User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL injection, which could let an attacker steal or manipulate data [confidence medium] |
wp-admin/edit-tags.php:109 |
| high | opengrep/php.lang.security.injection.tainted-sql-string: User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL injection, which could let an attacker steal or manipulate data [confidence medium] |
wp-admin/edit-tags.php:169 |
| high | opengrep/php.lang.security.injection.echoed-request: Echoing user input risks cross-site scripting vulnerability. You should use htmlentities() when showing data to users. [confidence medium] |
wp-admin/edit.php:329 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Repository profile
- Source lines: 557,386; test lines: 39,960
| Language | Lines |
|---|---|
| PHP | 507,837 |
| JavaScript | 89,179 |
| Shell | 265 |
| Python | 65 |