Penetration Tester

Orange Tsai Portfolio

Security researcher whose multi-part public research on Microsoft Exchange (ProxyLogon, ProxyOracle, ProxyShell, ProxyRelay) and PHP/web server vulnerabilities is published in full technical detail, with an active archive spanning from 2019 to the present.

Web Security ResearchVulnerability ResearchExchange ServerPHP Security

Location

Unlisted — probably wherever the wifi is strongest.

Skills

Web Security ResearchVulnerability ResearchExchange ServerPHP Security

What makes it work

A breakdown of the choices that make this portfolio stand out.

1

Named, real-world CVE-producing research

Publishing the actual research chain behind named vulnerability classes (ProxyLogon and related Exchange bugs) is a far stronger credential than describing "vulnerability research experience" generically — the work is independently verifiable via the CVEs it produced.

2

Bilingual publication (English and Traditional Chinese)

Publishing key research in two languages extends the audience deliberately rather than defaulting to English-only, widening the researcher's actual reach and influence.

3

Multi-year sustained research cadence

An archive running from 2019 to the present shows sustained output on hard problems rather than a single high-profile finding followed by silence.

What Penetration Testers can take from this

Specific, actionable tips to apply to your own portfolio — no generic advice.

  • If your research produced a named vulnerability or CVE, link the disclosure and technical writeup directly — it's independently verifiable in a way a resume bullet isn't.

  • Consider publishing significant research in more than one language if your work has an international audience — it meaningfully extends reach.

  • A multi-year archive of sustained research output is more convincing than one standout finding with nothing before or after it.

Case studies

Research into software much of the web runs on, including Exchange, PHP and major web servers. Findings go to the vendor first, get patched, and are then presented at top security conferences.

Case StudyadvancedOngoing since 2011

Conference Talks Archive (2011–2026)

Vulnerability researchWeb securityResponsible disclosureTechnical presentation

A dated list of every talk he has given, from local Taiwanese meetups in 2011 to international briefings. Each entry names the talk and every venue where it was presented. Recent titles cover Microsoft Exchange, Microsoft IIS, Apache HTTP Server, PHP and Windows character-encoding behavior.

Accepted research talks at Black Hat and DEF CON, year after year, are hard to earn. It shows peer-reviewed depth, and the skill of explaining complex findings to defenders.

  • Black Hat USA / DEF CON speaker across five years (2017–2022)

  • Four HITCON keynotes, most recently 2026

  • Talks given in both English and Traditional Chinese

Projects

Researchadvanced2019-2025

Microsoft Exchange Vulnerability Research

Exchange ServerHTTP Request SmugglingAuthentication BypassPrivilege EscalationCVE Disclosure

Multi-part vulnerability research on Microsoft Exchange Server covering ProxyLogon, ProxyOracle, ProxyShell, and ProxyRelay attack classes with full technical detail and CVE disclosures.

Demonstrates ability to conduct deep, production-impact security research at enterprise scale. CVE-producing research shows verification against real-world vulnerabilities rather than theoretical claims.

  • Named CVE classes (ProxyLogon, ProxyOracle, ProxyShell, ProxyRelay)

  • Full technical disclosure and attack chain documentation

  • Bilingual publication extending research reach

  • Multi-year sustained research output

ResearchadvancedPublished June 2024

CVE-2024-4577: PHP-CGI Disclosure

PHPPHP-CGIWindowsCoordinated disclosure

A vulnerability in PHP-CGI on Windows that he reported to the PHP project under DEVCORE's 90-day disclosure policy. His blog post says it bypasses the fix for a 2012 CVE and affects XAMPP for Windows by default. He calls it a side finding from preparing his Black Hat USA 2024 talk.

It shows a standard coordinated disclosure: a report to the vendor with a deadline, fixed releases before public details, and a public write-up pointing users to mitigations.

  • Official PHP advisory rated High, with his report quoted in it

  • Fixed in PHP 8.3.8, 8.2.20 and 8.1.29

  • Reported under a 90-day coordinated disclosure policy

Ready to build your portfolio?

Follow the Penetration Tester roadmap — skills, projects, and timeline to get hired.

Penetration Tester Roadmap