Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,110 of 9,110 pages
About the help in other languages
All help pages

Security updates and disclosure

What a business needs to know about security fixes for Exponential - which versions are supported, how fixes are published, how to tell whether a site is patched, who applies updates and how fast, and how to report a…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/businesses/security/security-updates-and-disclosure.md

On this page

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

  1. Which versions get fixes
  2. How fixes are published
  3. Is my site patched?
  4. Who applies updates, and how fast
  5. Reporting a vulnerability
  6. Extensions and everything around the site
  7. Checklist

Which versions get fixes

From SECURITY.md:

VersionSupported
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 olderno

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 main branch ... 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.14 or 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:

  1. The version the site runs (composer show se7enxweb/exponential), compared with the newest 6.0.x release.
  2. Whether any locked dependency has a known vulnerability (composer audit).
  3. Whether Setup > Upgrade check reports modified or missing files; it only reads (The upgrade check).
  4. Whether extensions are current; Setup > Updates and packages of ezupdate checks 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:

QuestionExample 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:

  1. Do not post it in the public issue tracker, the forums or social media.
  2. Report it privately to [email protected] (SECURITY.md), or as a private advisory on GitHub (https://github.com/se7enxweb/exponential/security/advisories/new).
  3. 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.
  4. 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.

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.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x