Security updates and disclosure
This page is for owners and managers who must make sure their site gets security fixes, and who need to know what
to do if someone finds a vulnerability. It explains the project's policy from SECURITY.md, what it means for your
budget and contracts, and how to report a problem the right way.
Note
Basics, not legal advice. If a vulnerability exposed personal data, notification duties may apply to you; ask a lawyer or your data protection officer at once.
Contents
- Which versions get fixes
- How fixes are published
- Is my site patched?
- Who applies updates, and how fast
- Reporting a vulnerability
- Extensions and everything around the site
- Checklist
Which versions get fixes
From SECURITY.md:
| Version | Supported |
|---|---|
6.0.x, the current line (main and the next tag cut from it) | yes |
6.0.x released tags (v6.0.0 to v6.0.14) | fixed by upgrading to the newest 6.0.x |
| 5.x, 4.x, 3.x and older | no |
If your site still runs a version from the eZ Publish years (3.x, 4.x or 5.x), it gets no security fixes. Moving it to Exponential 6 is a migration project; see Switching to Exponential.
How fixes are published
- "Security fixes are made on the
mainbranch ... and published with the next 6.0.x release." (SECURITY.md) - "A published tag is never changed: a fix for a problem in
v6.0.14or an earlier tag reaches you as the next release, not as a corrected copy of the old one." (SECURITY.md)
For a business this is good news: a version number always means the same code, so "are we patched?" has a clear answer, and a version you tested does not change under you (Security updates and disclosure for hosts).
Is my site patched?
Ask your administrator or host to tell you:
- The version the site runs (
composer show se7enxweb/exponential), compared with the newest 6.0.x release. - Whether any locked dependency has a known vulnerability (
composer audit). - Whether Setup > Upgrade check reports modified or missing files; it only reads (The upgrade check).
- Whether extensions are current; Setup > Updates and packages of
ezupdatechecks without changing anything (Automated updates with ezupdate).
A modified kernel file that nobody changed on purpose deserves a look (Compromised site).
Who applies updates, and how fast
The project sets no time frame for applying a fix; that is your decision or your host's (SLA options). Decide and write down:
| Question | Example answer to adapt |
|---|---|
| Who watches for releases? | our administrator, monthly and when the project announces one |
| Who applies them? | our hosting partner, under the contract |
| Within how long after a security release? | [number] working days, in a planned window |
| What if it cannot be applied at once? | the gap is documented with a date to close it |
| Who approves? | the site owner, or pre-approved for security releases |
Tip
Promise to apply a released fix within a time, not that a vulnerability will be fixed within a time: the second depends on the project, the first on you (SLA options).
How an update goes, in short: read the changelog, update a staging copy, then the live site, check file consistency, and test the front page and the sign-in (Security updates and disclosure for hosts). Budget the hours with Budgeting for upgrades and maintenance.
Reporting a vulnerability
If you, a customer or a researcher finds a security problem in Exponential:
- Do not post it in the public issue tracker, the forums or social media.
- Report it privately to [email protected] (
SECURITY.md), or as a private advisory on GitHub (https://github.com/se7enxweb/exponential/security/advisories/new). - Include the version, the PHP version, the engine (Velocity, FrankenPHP, Apache or nginx with PHP-FPM), the database, what an attacker can do and the steps to reproduce.
- Leave out passwords, secrets and personal data.
"You can expect a first answer within one business day." You are told whether the report is accepted and kept
informed while a fix is prepared (SECURITY.md). Problems in a third-party extension go to its maintainers
(When something goes wrong).
Tell your own staff and partners where to send such reports, for example in your account and password policy. Partners have their own escalation route (Escalations and security issues).
Extensions and everything around the site
A site is only as current as its weakest part:
- To do: Each extension is its own Composer package with its own releases.
- To do: PHP, the database server and the operating system need updates too.
- To do: Velocity's engine has its own releases.
- To do: Your own extensions and templates must be reviewed for unsafe patterns; the project's hardening notes list them (Security updates and disclosure for hosts).
Checklist
- To do: The site runs a supported 6.0.x version.
- To do: Someone named watches for releases.
- To do: The time to apply a security release is written in your contract or policy.
- To do: Updates go to a staging copy first.
- To do: The upgrade check is clean after each update.
- To do: Staff know to report vulnerabilities privately to [email protected].
- To do: A plan exists for informing customers if their data was affected.
Related pages
- Release line and support policy
- Upgrades without surprises
- Security review checklist for hosts
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.