ICYMI, our hashtag#vulnerabilityresearch team found 2 vulnerabilities in phpBB that let an attacker walk in _without_ a password:

_CVE-2026-48611 (9.4): one unauthenticated request, any account, including admin. Default installations. No user interaction. Went unnoticed for over a *decade*.

_CVE-2026-48612 (8.3): if OAuth is configured, an attacker can silently bind their credentials to a logged-in user's account. No click needed from the victim. A hidden image tag in a post is enough.

Full technical write-up, potential impact & detection guidance 👇👇👇

https://pentest-tools.com/research/phpbb-authentication-bypass

hashtag#infosec hashtag#ethicalhacking

Knowing something was _off_ before you could prove it.
Knowing when the _obvious_ path was the wrong one.
Knowing _when_ to keep pulling.

No dashboard tracks any of that.

Which means the skills that actually separate good practitioners from the rest stay invisible.

Which underrated skill improved your offsec intuition & attacker mindset?

#offensivesecurity #penetrationtesting #ethicalhacking

WordPress may be losing market share, but it still runs 41.5% of the web. And that means:

older installs shift from "active priority" to "legacy concern"
patching slows down
monitoring gets disabled
plugins nobody's touched in years keep their coat of dust.

But 41.5% of all websites is NOT a footnote.

It's an *enormous*, aging, plugin-heavy attack surface.

This is why our WordPress Scanner comes in handy to:
✅ map known vulnerabilities across plugins, themes & versions
✅ run scheduled scans automatically, so new issues surface with zero manual work
✅ use scan results to feed your compliance or vulnerability assessment reports.

Curious what it can deliver?

Check out the report attached or run a FREE, non-intrusive scan on any WordPress site. 👇👇

https://pentest-tools.com/cms-vulnerability-scanning/wordpress-scanner-online-wpscan

#vulnerabilityassessment #wordpress

Most organisations that fumble #cybersecurity incidents have perfectly adequate technical controls. What they're missing is a CEO, a General Counsel, and a CISO who've sat in a room together and had an uncomfortable conversation before the crisis hit.

Sergiu Zaharia, PhD, our CISO, has run crisis simulations across military intelligence, telecoms, and regulated sectors for 25 years.

The most common finding across these experiences was never technical.

It was *decisional*:

Who has authority to take a production system offline?
When does legal need to be in the room?
Do you pay the ransom?

Teams that haven't practiced these questions under pressure don't answer them well when push comes to shove.

He shares the full argument in the latest Intelligent CISO special report, alongside CISOs from Zscaler, Mimecast, SailPoint, and other passionate leaders 👉 https://magazine.intelligentciso.com/IDKd/p48/p46

Office Hours this Wednesday: pre-audit validation.

Jan Pedersen walks through finding and fixing what's there before a formal pentest or audit does, so nothing in the report surprises you.

What to check first, telling a real finding from a false one, and proving what you closed by comparing one scan to the next.

30 min live, 15 min Q&A.
Wed Jun 17, 2026, 6 PM Bucharest / 4 PM London / 11 AM New York / 8 AM LA

https://zoom.us/webinar/register/5417815287714/WN_A6m_8zzfSHiuRx9AR3SZkA

AI is finding vulnerabilities faster than most organizations can patch them. That's not a tooling problem.

Daniel Bechenea, security manager at Pentest-Tools.com, in ITPro: "More patches, shipped faster. But that's the upstream change. The downstream problem is, none of that vendor-side progress makes the organizations receiving those patches any faster at deploying them."

The gap between knowing and doing just got more consequential.

Kate O'Flaherty's full article is here for the reading

https://www.itpro.com/security/why-patching-velocity-matters-as-claude-mythos-supercharges-vulnerability-discovery

You don't trust a finding until you've reproduced it. That's the job in #offensivesecurity.

AI discovery produces findings FAST. But it doesn't tell you what's exploitable in your context.

Volume goes up. 📈 Validation stalls. 🚧

Faster discovery, same validation. Where's the real bottleneck now?

Only 8.7% of developers say vulnerability testing keeps pace with their development work.

We asked 241 of them how AI-assisted coding has changed what they ship.

A few things stood out:
✅ 76% use AI coding tools always or usually
✅ 30% say they don't have enough time to review AI-generated code thoroughly
✅ 51% see vulnerabilities surface in AI-assisted code after deployment

The validation window between writing code and confirming whether it's safe to deploy is shrinking. The offensive security work that closes that window matters more, not less.

If your team is absorbing more deployed code than it can review, where does the evidence trail break first: at detection, at validation, or at retest?

Discover The shape of vulnerabilities to come: more subtle, context-dependent errors 👉 https://pentest-tools.com/insights

The gap between testing something and *proving* it, is the part nobody signed up for.

So here's how we tackle proof for compliance at Pentest-Tools.com

Audit-ready evidence comes down to 4 things:

✅ Visibility beyond the "wall": passwords, screenshots, and more

🔁 Reproducibility: enough detail to recreate & retest

🎯 Context: why a finding matters, not just its score

📄 Clarity: one report that works for the auditor, the CISO & the engineer

Wanna see how it comes together? Link is here https://pentest-tools.com/usage/compliance

🏴‍☠️ New #offensivesecurity research: phpBB authentication bypass discovered by Pentest-Tools.com! And it packs *two* vulnerabilities. 👇👇👇

⚡PTT-2026-004 (CVSS 9.4 - critical): one HTTP request, a target username, a wrong password phpBB never checks. You get back a valid session cookie for that account.
Admins included.
Works on every default phpBB install up to and including 3.3.16, no prior access needed.

The vulnerable code path got introduced more than 10 years ago and survived multiple major releases and security reviews before Alex Dan, offsec researcher at Pentest-Tools.com, found it along with...

⚡PTT-2026-005 (CVSS 8.3 - high) which chains two OAuth defects for a silent account takeover on sites with OAuth configured. In some cases, the victim doesn't need to click anything - an image tag embedded in a forum post is enough to trigger it.

⬇️⬇️⬇️

Full technical breakdown & mitigation steps 👉 https://pentest-tools.com/research/phpbb-authentication-bypass "