WordPress/WordPress-Develop
WordPress/WordPress-DevelopClick 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.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Code quality scan: 29 findings (C, 75/100)
Hi @WordPress, an automated scan of this repository surfaced **29 code-quality findings** that may be worth a look.
Full details, severity filters, and per-file context are at the link below — feel free to close this issue if it isn't useful to you.
## Full interactive report
**https://repobility.com/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/**

## At a glance
- **Score**: `75/100` • **Grade**: `C`
- **Scanned**: `2026-05-16 13:30 UTC`
- **Lines of code**: 181,063
- **Total findings**: 29
- **Security-tagged**: 1
- **Credential / secret patterns**: 1
## Top issues, with file & line
_These are deterministic rule-based findings — the file paths and line numbers below are real and can be verified in your tree._
1. **[critical]** [SEC001] Hardcoded Password: Hardcoded password found in source code. — `src/js/_enqueues/admin/auth-app.js:84`
_Use environment variables or a secrets manager._
2. **[high]** [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches. — `src/wp-activate.php:128`
_Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400)…_
3. **[high]** [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches. — `src/wp-admin/about.php:180`
_Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400)…_
4. **[high]** [SEC029] Server-Side Request Forgery (SSRF) — outbound HTTP from user input: Outbound HTTP request to a user-controlled URL without allowlist validation. Attackers can probe internal services (169.254.169.254 metadata, internal Kubernetes endpoints, file:// URIs), exfiltrate data, or pivot through your network. SSRF is OWASP A10:2021 and a frequent foothold in cloud breaches. — `src/wp-admin/edit-form-comment.php:186`
_Validate the URL against an allowlist BEFORE fetching: ALLOWED = {'images.example.com', 'cdn.example.com'} host = urlparse(url).hostname if host not in ALLOWED: abort(400)…_
5. **[high]** [SEC027] XML External Entity (XXE) — Node.js xml parsers: Node.js XML parsers can expand external entities if not configured. libxmljs in particular has had XXE CVEs. — `src/js/_enqueues/wp/sanitize.js:30`
_Pass `noent: false` to libxmljs. Avoid xml2js or pass explicit secure config. Prefer parsers that don't expand external entities at all._
See all 29 findings, with severity filters and AI fix prompts: **https://repobility.com/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/**
---
**What is this?** [Repobility](https://repobility.com) is a research project that scans public repositories with a multi-layer static analyzer (rule-based, no AI hallucinations) and learns code-quality patterns across a broad cross-repo corpus. This is **not a sales pitch** — there's no paywall, no signup required to view the report, and no payment ask. If the findings aren't useful, please close this issue and we won't post again.
**To re-run after fixes land:** paste your repo URL at [repobility.com](https://repobility.com) — fresh scan, free.
_Issue filed via the public Repobility report at https://repobility.com/scan/17978a6a-1088-4d9a-a761-73a403ca6a42/._
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.