Editorial Policy

Our goal is to make PHP security news understandable without overstating risk or claiming to have tested individual websites.

Source priorities

We use official PHP announcements, vendor advisories, CVE records, and established public security guidance. Links to source materials are provided where practical.

Technical accuracy

We distinguish affected version ranges, fixed releases, configuration prerequisites, and unverified assumptions. A CVE affecting a PHP release does not prove that a particular site is vulnerable.

Corrections and updates

Security details can change. We review corrections when new official information becomes available, but do not promise continuous real-time monitoring on the public site. Send correction requests via Contact us.

Independence

PHP Secure is not affiliated with the PHP Group. Mentions of Prusly identify an optional AI tool for code and error explanations, not an official PHP security authority.