← Back to scan
File as GitHub Issue repo: WordPress/WordPress-Develop

Push this scan report to WordPress/WordPress-Develop

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Server-Side Request Forgery (SSRF) — outbound HTTP from user input

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
CRIT SEC001 [SEC001] Hardcoded Password: Hardcoded password found in source code. src/js/_enqueues/admin/auth-app.js:84
HIGH SEC027 [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers can expand … src/js/_enqueues/wp/sanitize.js:30
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… src/wp-admin/edit-form-comment.php:186
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… src/wp-admin/about.php:180
HIGH SEC029 [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTT… src/wp-activate.php:128
MED CFG006 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build art… —
MED SEC015 [SEC015] Insecure Randomness for Security: Weak PRNG used in security-sensitive context. … src/js/_enqueues/wp/embed.js:99
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/js/_enqueues/admin/user-profile.js:553
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/js/_enqueues/admin/privacy-tools.js:323
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. src/js/_enqueues/admin/media-upload.js:61
MED WEB003 Public web service has no security.txt .well-known/security.txt
MED WEB015 Public web app has no Content Security Policy index.html
MED CORE_LARGE_FILES Average file size is 624 lines (recommend <300) —
LOW AIC003 Duplicated implementation block across source files src/js/_enqueues/wp/widgets/text.js:285
LOW AIC003 Duplicated implementation block across source files src/js/_enqueues/wp/widgets/text.js:47
LOW AIC003 Duplicated implementation block across source files src/js/_enqueues/wp/widgets/media.js:698
LOW WEB002 Public web app has no sitemap sitemap.xml
LOW WEB008 Public docs site has no llms.txt llms.txt
LOW WEB011 Public web app has no humans.txt humans.txt
LOW CORE_NO_LICENSE No LICENSE file —
Reset to top 5 20 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `WordPress/WordPress-Develop`

**Score: 75/100 (C)**  ·  29 findings  ·  scanned 2026-05-16 13:30 UTC  ·  181,063 LOC

| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 4 |
| MEDIUM | 8 |
| LOW | 7 |

📊 [Full filterable report](https://repobility.com/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/)  ·  ![scorecard](https://repobility.com/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/report.png?v=1778938251-s2)

### Top findings

1. **CRITICAL** `SEC001` — Hardcoded Password
   `src/js/_enqueues/admin/auth-app.js:84` · A07:2021 Identification & Authentication Failures
2. **HIGH** `SEC027` — XML External Entity (XXE) — Node.js xml parsers
   `src/js/_enqueues/wp/sanitize.js:30` · A05:2021 Security Misconfiguration (XXE)
3. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `src/wp-admin/edit-form-comment.php:186` · A10:2021 SSRF
4. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `src/wp-admin/about.php:180` · A10:2021 SSRF
5. **HIGH** `SEC029` — Server-Side Request Forgery (SSRF) — outbound HTTP from user input
   `src/wp-activate.php:128` · A10:2021 SSRF

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/_
Premium account
This scan was submitted by a Enterprise-tier account. Premium accounts have full outreach control â Repobility doesn't pre-fill the 'file as GitHub issue' button for paid users. You can still file the issue manually using the markdown body above (Copy markdown), or contact us if you'd like batch-filing enabled for your account.
Already filed
This repo publishes a SECURITY.md policy and the scan contains 5 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'WordPress/WordPress-Develop' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Cancel

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.