HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Qbix
proxy
C2026–2026
Qbix / proxy

proxy

Simple web server proxy to protect PHP code bases from known vulnerabilities.

3Distinct people
6Mentions
0Explicit recommenders
14GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple web server proxy to protect PHP code bases from known vulnerabilities.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour6 dated mentions

Observed mentions: 2026-10-21 13:41:30 UTC to 2026-10-22 18:50:54 UTC.

012026-10-21 13:00:00 UTC to 2026-10-21 14:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsOct 21, 13:002026-10-21 14:00:00 UTC to 2026-10-21 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-21 15:00:00 UTC to 2026-10-21 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-21 16:00:00 UTC to 2026-10-21 17:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-21 17:00:00 UTC to 2026-10-21 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-21 18:00:00 UTC to 2026-10-21 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-21 19:00:00 UTC to 2026-10-21 20:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-21 20:00:00 UTC to 2026-10-21 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-10-21 21:00:00 UTC to 2026-10-21 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-21 22:00:00 UTC to 2026-10-21 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-21 23:00:00 UTC to 2026-10-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 00:00:00 UTC to 2026-10-22 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 01:00:00 UTC to 2026-10-22 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 02:00:00 UTC to 2026-10-22 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 03:00:00 UTC to 2026-10-22 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsOct 22, 03:002026-10-22 04:00:00 UTC to 2026-10-22 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 05:00:00 UTC to 2026-10-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 06:00:00 UTC to 2026-10-22 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 07:00:00 UTC to 2026-10-22 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 08:00:00 UTC to 2026-10-22 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 09:00:00 UTC to 2026-10-22 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 10:00:00 UTC to 2026-10-22 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 11:00:00 UTC to 2026-10-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 12:00:00 UTC to 2026-10-22 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 13:00:00 UTC to 2026-10-22 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 14:00:00 UTC to 2026-10-22 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 15:00:00 UTC to 2026-10-22 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 16:00:00 UTC to 2026-10-22 17:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2026-10-22 17:00:00 UTC to 2026-10-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-10-22 18:00:00 UTC to 2026-10-22 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 22, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 21, 13:002026-10-21 13:00:00 UTC2026-10-21 14:00:00 UTC110
Oct 21, 14:002026-10-21 14:00:00 UTC2026-10-21 15:00:00 UTC000
Oct 21, 15:002026-10-21 15:00:00 UTC2026-10-21 16:00:00 UTC000
Oct 21, 16:002026-10-21 16:00:00 UTC2026-10-21 17:00:00 UTC101
Oct 21, 17:002026-10-21 17:00:00 UTC2026-10-21 18:00:00 UTC000
Oct 21, 18:002026-10-21 18:00:00 UTC2026-10-21 19:00:00 UTC000
Oct 21, 19:002026-10-21 19:00:00 UTC2026-10-21 20:00:00 UTC101
Oct 21, 20:002026-10-21 20:00:00 UTC2026-10-21 21:00:00 UTC101
Oct 21, 21:002026-10-21 21:00:00 UTC2026-10-21 22:00:00 UTC000
Oct 21, 22:002026-10-21 22:00:00 UTC2026-10-21 23:00:00 UTC000
Oct 21, 23:002026-10-21 23:00:00 UTC2026-10-22 00:00:00 UTC000
Oct 22, 00:002026-10-22 00:00:00 UTC2026-10-22 01:00:00 UTC000
Oct 22, 01:002026-10-22 01:00:00 UTC2026-10-22 02:00:00 UTC000
Oct 22, 02:002026-10-22 02:00:00 UTC2026-10-22 03:00:00 UTC000
Oct 22, 03:002026-10-22 03:00:00 UTC2026-10-22 04:00:00 UTC000
Oct 22, 04:002026-10-22 04:00:00 UTC2026-10-22 05:00:00 UTC000
Oct 22, 05:002026-10-22 05:00:00 UTC2026-10-22 06:00:00 UTC000
Oct 22, 06:002026-10-22 06:00:00 UTC2026-10-22 07:00:00 UTC000
Oct 22, 07:002026-10-22 07:00:00 UTC2026-10-22 08:00:00 UTC000
Oct 22, 08:002026-10-22 08:00:00 UTC2026-10-22 09:00:00 UTC000
Oct 22, 09:002026-10-22 09:00:00 UTC2026-10-22 10:00:00 UTC000
Oct 22, 10:002026-10-22 10:00:00 UTC2026-10-22 11:00:00 UTC000
Oct 22, 11:002026-10-22 11:00:00 UTC2026-10-22 12:00:00 UTC000
Oct 22, 12:002026-10-22 12:00:00 UTC2026-10-22 13:00:00 UTC000
Oct 22, 13:002026-10-22 13:00:00 UTC2026-10-22 14:00:00 UTC000
Oct 22, 14:002026-10-22 14:00:00 UTC2026-10-22 15:00:00 UTC000
Oct 22, 15:002026-10-22 15:00:00 UTC2026-10-22 16:00:00 UTC000
Oct 22, 16:002026-10-22 16:00:00 UTC2026-10-22 17:00:00 UTC110
Oct 22, 17:002026-10-22 17:00:00 UTC2026-10-22 18:00:00 UTC000
Oct 22, 18:002026-10-22 18:00:00 UTC2026-10-22 19:00:00 UTC101

What Hacker News says

6 sources
It's bulletproof, in the same way that my open window is bulletproof because a bullet will fly right through it and not damage the glass. Additionally, the author isn't engaging on this site in good faith. See this thread https://news.ycombinator.com/item?id=50181138 from yesterday, where egregious vulnerabilities in this project were pointed out, at which point the author force pushed to hide the history, failed to fix the vulnerabilities pointed out (e.g. https://github.com/Qbix/proxy/blob/5a9f8a96f4bdaaaa5444b6986... still doesn't match the PHP multipart parser, so the whole defense can be mooted by switching to a space as the delimiter). This is an exemplar of slop.
In Amazon identifies Oct 17 PHP2Shell exploitation prior to public disclosure
1792584762 | Show HN: Timeminator Self-hosted open-source time tracker (PHP, Docker) | https://github.com/freshNfunky/Timeminator-Community | https://news.ycombinator.com/item?id=50179595 | 1 comment 1792585635 | Governments Take Websites Offline After PHP Security Warnings | https://www.bloomberg.com/news/articles/2026-10-21/governmen... | https://news.ycombinator.com/item?id=50179760 | 1 comment 1792585888 | Dutch National Cyber Security Center is Offline because it uses PHP | https://www.ncsc.nl/actueel | https://news.ycombinator.com/item?id=50179828 | 58 comments 1792586839 | Show HN: Passive exposure check for the PHP2Shell flaws (CVE-2026-109618/109619) | https://php2shell.xyz | https://news.ycombinator.com/item?id=50179999 | 0 comments 1792587855 | Show HN: Managed EmDash CMS hosting on Cloudflare, no PHP, no server | https://host
Read the rest
myemdash.com/ | https://news.ycombinator.com/item?id=50180254 | 0 comments 1792589908 | Check/probe tool for PHP CVE-2026-109618/619 | https://php2shell.site/news.ycombinator.com/11c22360e8df83b4 | https://news.ycombinator.com/item?id=50180769 | 0 comments 1792589952 | PHP patches have been released | https://www.php.net/archive/2026.php | https://news.ycombinator.com/item?id=50180783 | 0 comments 1792590090 | Simple Proxy to secure your PHP from vulnerability CVE-2026-109618 | https://github.com/Qbix/proxy | https://news.ycombinator.com/item?id=50180810 | 0 comments 1792590108 | PHP Security advisory: Critical remote code execution vulnerabilities | https://www.php.net/archive/2026.php | https://news.ycombinator.com/item?id=50180818 | 0 comments
In PHP2Shell: AI uncovers critical RCE in PHP
I'm going to engage only because I do not wish others to come across this project and think it's serious. I did open the project and read the code, and I did throw it into an LLM as I previously said for some very basic security posture checks, and found a number problems immediately, but I don't trust them (and neither should you, which is part of the problem here), so I went digging a bit deeper. I don't have the time to go through all of them, so here's a big one of my own finding: There's a parser differential in how multipart boundaries are handled, your proxy only deals with ;, the PHP interpreter accepts , as well, and the proxy will pass it through unchanged to the upstream. That's a full bypass of what the proxy is trying to do. https://github.com/Qbix/proxy/blob/main/src/sanitize.c#L41 https://github.com/php/php-src/blob/master/
Read the rest
main/SAPI.c#L162 The article linked from your own README (https://sansec.io/research/php2shell) has a better partial mitigation in existing, battle-tested reverse proxies. Even still, as that article says, everything here is a partial mitigation. The description of the issues in your project's README is an inaccurate understatement of the severity of the issues. "CVE-2026-109618 — heap use-after-free in the session.upload_progress handler" is an incomplete understatement of the issue, the session.upload_progress handler is only one of a number of potential exploitation paths. https://github.com/php/php-src/security/advisories/GHSA-w8hw... has some hints at other paths, of which there are many. From an LLM, and quickly validated by me, a heap overflow, likely an RCE. > src/http.c:101-116 and src/util.c:9 Attacker supplied value in strtoul, the size-limit checks are unsigned addition that can wrap, and you can follow the chain from there. > or better yet submit a request. This project is not deserving of fixing, it should just be deleted and direct people to more serious documentation of fixes and mitigations. This code is clearly AI-generated slop, it is not my responsibility to fix your project. > I could understand if you actually at least clicked and looked at the repository, and read what it’s about. But you chose to simply write generic text without looking at anything. You want to discourage people from protecting their servers, in order to feel good about yourself. What amount of effort have you put into understanding what you’re even talking about? Every accusation is an admission.
In PHP 8.2.35

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.