xtekky/gpt4free
xtekky/gpt4freeClick 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.
Object-level route lacks visible authorization: A route with an object id-like parameter d
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `xtekky/gpt4free` **Score: 59/100 (C+)** · 57 findings · scanned 2026-05-15 03:47 UTC · 54,848 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 6 | | MEDIUM | 31 | | LOW | 6 | 📊 [Full filterable report](https://repobility.com/scan/00245f64-d50c-4146-ae35-895f3151f1fc/) ·  ### Top findings 1. **HIGH** `SEC013` — Path Traversal — User Input in File Path `g4f/tools/files.py:297` · A01:2021 Broken Access Control (path traversal) 2. **HIGH** `AUC003` — Object-level route lacks visible authorization: A route with an object id-like parameter d `g4f/gui/server/backend_api.py:644` · CWE-639 · API1:2023 Broken Object Level Authorization 3. **HIGH** `AUC003` — Object-level route lacks visible authorization: A route with an object id-like parameter d `g4f/gui/server/backend_api.py:547` · CWE-639 · API1:2023 Broken Object Level Authorization 4. **HIGH** `AUC003` — Object-level route lacks visible authorization: A route with an object id-like parameter d `g4f/gui/server/backend_api.py:543` · CWE-639 · API1:2023 Broken Object Level Authorization 5. **HIGH** `AUC003` — Object-level route lacks visible authorization: A route with an object id-like parameter d `g4f/gui/server/backend_api.py:393` · CWE-639 · API1:2023 Broken Object Level Authorization --- **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/00245f64-d50c-4146-ae35-895f3151f1fc/_
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.