Skip to content

Stack vulnerabilities

51 help pages

A site report ends with a Stack vulnerabilities section. It lists known vulnerabilities (CVEs) that match the versions of the site's PHP, web server and database: PHP, Nginx, Apache, MySQL, MariaDB and PostgreSQL. Other products (LiteSpeed, Microsoft IIS, Caddy and SQLite) are listed but not checked yet. The wording is always "matches known vulnerabilities", never "is vulnerable": a match is made by version, and a vendor may have patched a problem without changing the version number.

  • Stack versions shows the version of each component at the end of the month, and whether it was reported by the site or declared in the site settings. Not shared means the site owner turned off Report platform versions for that month, and the component's open matches are left out. A product Sentinel does not match yet, such as LiteSpeed, Microsoft IIS, Caddy or SQLite, shows Not checked yet. A component with no version shows Not reported or Version unknown. Some managed or forked database builds, such as Amazon Aurora MySQL, Vitess or PlanetScale, TiDB, Percona Server and MariaDB Enterprise Server, use version numbers that do not follow the upstream releases, so Sentinel cannot match them. They also show Version unknown, never as clear of vulnerabilities.
  • Coverage tiles under the stack sentence in the report summary: Sites checked (for example "3 of 4", with "Full coverage" or "Partial coverage"), Open at month end (the open matches, or "None") and Not reported (sites whose web server and database were not shared, labelled "Platform sharing turned off"). Each tile states its meaning in words as well as colour. Sites on connectors older than 1.4.0 are not counted as not reported.
  • Open at the end of the period lists each match with its CVE, component, version, severity, Known exploited flag, the version that fixes it and when Sentinel first showed it. While Sentinel's Ubuntu and Debian checks are on, a match that Ubuntu or Debian says is not fixed in your build shows the vendor's fixed package build as the fix, when the version Sentinel recorded for that month includes the package build; otherwise the usual fixed version shows.
  • Resolved this month lists matches that ended in the month, how (for example upgraded to a fixed version, Fixed by the operating system vendor's update or Operating system vendor says not affected) and the date.
  • Acknowledged as not affecting the site lists matches your team marked as not affecting the site, with the reason, note, who and when. A decision from an earlier month that is still in force is included, with its original date.
  • Acknowledgements withdrawn or reopened this month appears only when there is one. It gives the date, why it ended and the result. Two reasons come from the Ubuntu and Debian checks: Operating system vendor now lists this as affected (the vendor says your build still needs a fix, or has none yet) and Operating system vendor checks switched off.

The figures are as they stood at the end of the month in the organisation owner's time zone, so a report made again later still shows that month as it was. Fixed in is the exception: it describes the vulnerability as known when the report is made, including the vendor's fixed build. Matches that are probably vendor fixes (low confidence) are never shown. The Summary has one Stack: line under the headline figures, counting the sites in scope with open matches, the open matches by severity and the acknowledged matches. The section is printed and is in the PDF. Reports issued before this section existed do not have it. Anyone who can read a report sees it; no role, permission or plan changes apply.

Repository security in reports

Where Patching, Deep scan and the security scan are on for your organisation, each site report has a Repository security section after Stack vulnerabilities, and the Summary has a Repository security: line and a Time to fix repository findings table. If you see none of these, your organisation does not have the check yet, your role does not read Patching, or Patching is off for your organisation, and the report is the same as before. Reports issued before this section existed show nothing.

  • Facts. Scans this period (and how many did not finish), the last successful scan, how many findings were open at the end of the period, and the size of the software list.
  • Open findings by kind and severity. A table counts the findings open at the end of the period under Dependencies, Code to review and Looks like a credential, by severity. Critical and high findings are then listed with the finding, where it is, its severity, Fixed in and when it was first seen. A credential's location is never printed: it reads Not shown in reports. Findings rated medium or lower are only counted: "And N more, rated medium or lower. The full list is in Deep scan."
  • Fixed this period. Each fixed finding says how: Pull request #N, merged, No longer found by the scan or Advisory no longer matches, with the days it was open.
  • Exceptions. Findings with a decision: Dismissed, Accepted risk until a date, False positive, or one that ended and was reopened, with the reason, who decided and when. An accepted risk past its end date counts as open from that date.
  • Sites Sentinel could not check. A site with no repository says "Not checked: no repository is connected to this site for Patching." A repository that had not been scanned by the end of the period also reads as not checked. Neither is a clear result.
  • Summary. The Repository security: line gives sites scanned, open findings by severity, fixed this month and exceptions in force. Time to fix repository findings lists dependency findings by severity, then Code to review and Looks like a credential, with how many were fixed this period, the typical (median) time to fix, the longest, how many are still open and the oldest open. The time runs from the start of the last time a finding was open (found, or reopened) to its fix. Dependency findings with no rating are counted but not timed. These figures are not judged against SLA targets and do not change the result.
  • As at the end of the month. Figures are read from the scan history at the end of the month, so a report made again later says the same. Only the repository and branch the site uses now are counted.
  • Who sees it. Only people whose role reads Patching. Everyone who sees the section sees code paths and exception reasons, so think before sharing a printed or downloaded report outside your team.
  • Printing. The facts and the count table stay on one page; the lists may run over pages. The downloaded PDF has one bookmark, Repository security. An issued version keeps what it showed on the day it was issued; if the check is later switched off, the section is left out until it is switched on again.

Print and download

Use Print to open the browser print dialog. The report is designed for a white A4 document in either dashboard theme. Every ledger row is printed, with the release lines open; a deployment that fits on a page is kept on one page, and the column headings repeat when the table runs over. The downloaded PDF has a bookmark for each block of the report: on a site report Verdict, Changes, Outstanding, Evidence (when there are evidence tables) and How this report is measured; an organisation report has a branch per site. Use Download PDF when offered. This requires an export permission and the enabled PDF service. Wait while the file is prepared; follow any reported failure and retry when appropriate.

A normal User can read and print an accessible report. Site managers and administrators normally also have PDF export permission. Always check the organisation, client, month, and version before sharing a file.

Issue, regenerate, and add notes

An administrator can issue a finished month or regenerate it from current evidence. Regeneration creates another version; it does not overwrite the earlier one. The running month cannot be issued.

An authorised site manager or administrator can add a note to the latest issued report. Saving a note creates a version with the same figures. Regeneration can update evidence and branding, while earlier versions remain in the archive. Report version details identify the preceding version and any reason. Older reports can show Recorded as applied when their stored rows have no observation evidence. Use a regeneration reason when needed to explain the new version.

Sentinel support can also regenerate an issued report for you, for example to correct a fault. The new version appears in Archive like any other version, and the earlier version stays. Its reason reads "Regenerated by Sentinel support" and no author is shown. The note carries over. Sentinel does not email this version automatically.

Open Archive to inspect issued versions and return to the required report. The Covers column names the site, or shows a summary for reports issued for a client or the whole organisation. Those earlier summary reports can still be opened, printed and downloaded. A stored version preserves its report figures even if a site or SLA changes later. Automatic issue is designed to run two days after month end where scheduled reporting is enabled, and issues one report per site plus the organisation report used for the monthly email; check Archive for the actual result.

Monthly report email

Where monthly email is enabled for the service, the first scheduled report for the whole organisation is emailed from day 3 of the next month, in the organisation owner's time zone. It goes to current organisation administrators with verified email addresses, permission to read reports in that organisation and report access. The read permission is checked before the email is queued and again before it is sent. Paid report access can come from an Agency billing holder. Readers and site managers do not receive these emails. Older months are not sent as a backlog. If a correction or note replaces the first report before its email is queued, automatic delivery skips that report. An eligible administrator can explicitly email an issued version that was not emailed. Sentinel support can also resend the current version's email to the organisation's current eligible administrators. The email and eligibility are the same as above, so an administrator who turned the monthly email off does not receive it. An administrator who already had that version receives another copy.

In Reports, use Monthly report email → the Email me each new report switch to change your choice for the selected organisation. Where the service has turned email settings on, the same choice is also on the Email settings page, and changing it in either place changes both (see Email settings). The switch is your own choice, not the whole organisation's. It starts on and is separate from site alerts and release/fix emails. Turning it on does not make an ineligible account eligible. The choice also applies when an administrator explicitly sends a report. If the preference cannot load, reload the page. If saving fails, try again; the previous choice remains in place. While monthly email is not enabled for the service, Reports does not show the Monthly report email section or its send button.

If your account is not eligible, the card shows You do not get this email (or Confirm your email address first) with the reason, beside the switch. It does not show who the email went to or any send button.

  • Your email address is not confirmed yet: select Send a confirmation link. The page says "A confirmation link is on its way to your email address. Open it, then reload this page. If it has not arrived in a few minutes, send another." Use Send another link if it does not arrive. If a link was sent moments ago, it says "A link was sent a moment ago. Wait a few minutes, then try again." This also works for older accounts that were never asked to confirm. The link goes to your account's current address.
  • Only organisation administrators get this email: viewers and site managers see this reason.
  • Your role in this organisation cannot read reports: an administrator whose report access was removed sees this.
  • Reports are not available for this organisation right now, or The organisation that pays for reports is not available right now: nothing to change on your side; try again later or contact Sentinel support if it stays.

The email lists the month's site reports with a link to each, up to 25. When there are more, it says how many more are in Reports. Site reports are not emailed on their own.

The email describes the exact issued version, including its reporting period, time zone, cutoff and evidence limits. Later findings do not change that email or report. Unknown coverage does not mean zero activity. Partial coverage can show At least counts. Older versions without a stored digest say the activity digest is unavailable.

Corrected reports, note changes, client and site reports and manually issued reports are not emailed automatically.

What an administrator sees. If you are an organisation administrator who gets this email, the card shows the issued version you are looking at ("Version N") with a coloured summary and a short trail: Sending, Handed to mail service, Delivered. The summary reads, for example, Sending to 2 people, Handed to the mail service for 1 person, Delivered, Delivered to 1 of 3 people, This version has not been emailed, Nobody was set to get this version or Not sent. Below it, a list shows each recipient with a name, an address, "(you)" next to your own row, and one label:

  • Sending or Trying again: Sentinel is still working on it. When the mail service is busy, Sentinel tries again by itself.
  • Handed over: the mail service took the email. It has not yet said whether it arrived. Where the service does not report delivery, rows stay here.
  • Delivered: the person's mail server accepted it. This is not proof that they read it or that it avoided junk mail.
  • Delayed: their mail server asked to try later. The mail service keeps trying.
  • Bounced, Not delivered or Blocked: it did not arrive. The row says why, for example that the address bounced before.
  • Marked as spam: it was delivered, and the person marked it as spam.
  • Unknown: Sentinel cannot tell if the mail service got it, so it will not send it again.
  • Not sent: it never went out, with a reason such as "They turned this email off before it went out." or "They are no longer an organisation administrator."
  • No longer tracked: the sending record was removed, for example with a deleted account.

If a deleted account removed someone's sending record, the summary counts them as unknown, never as delivered.

A person who has left the organisation shows as Former member with no name or address. If someone's address changed after the email was prepared, their row says "Address changed after this email was prepared".

The card checks again by itself: every few seconds while an email is sending, and every 30 seconds while it waits for delivery news, for up to 30 minutes after the hand-over. Then it stops, and a row still without news stays Handed over. If the tab was in the background, it checks once when you come back. Select Check now to look again at any time.

Delivered, bounced and similar news comes from the mail service, and only where delivery tracking is set up for the service. Where it is not, rows stay Handed over.

When the version you are viewing was not emailed, for example a corrected version or a note change, the card shows Email version N. Select it to send that version to the administrators who get this email. The button is not shown for a version that was already emailed. If the send result cannot be confirmed, use Check now before trying again. Delivery news does not prove the report was read. Temporary failures can be retried within the delivery window. Removed members, changed or unverified addresses, lost access and disabled preferences can stop a pending delivery. If access is removed while email acceptance is unknown, the status can be Uncertain because the email might already have been accepted. A definite refusal without an earlier uncertain outcome can still show Revoked. Uncertain does not confirm sending or inbox delivery and does not cause that issued version to be resent. Recorded acceptance remains visible even if the recipient later loses access.

Each issued version is emailed once from the Reports page. No recipients is also a final audience decision. Changing membership or a preference does not resend that version or add recipients. Issue a new version and explicitly send it when a changed audience needs the report.

Account deletion can remove delivery history. The list then shows only the people whose records remain. If every record was removed, the card says the version was emailed and that its sending records were removed. This does not cause a resend.

Select Open issued report in the email and sign in. Your current permissions and report access still apply. If another organisation is active, use Switch organisation when prompted. No report loads until the organisation matches. If that organisation is unavailable, check that you used the correct account. To check current status, select View current site status in the email, sign in and select the report's organisation on Sites. Current status does not change the issued figures.

Report branding

Administrators with branding permission can use Branding when the plan permits changes. Enter company and contact details, address, country, tax identifier, header text, footer text, and the Sentinel attribution choice. Review the preview and save. These report details are separate from billing details. Tax identifiers are printed as entered; they are not verified against a register.

Logo upload is available only when enabled. Follow the form's PNG, size, dimension, and rights-confirmation requirements. You can replace or remove a logo. A new branding choice affects newly generated reports; issued versions retain their stored branding, subject to removal of disputed logos.

Legacy Free accounts cannot open reports. Reports require baseline access; retained Solo and Studio access uses Sentinel branding. Agency and Enterprise allow their own branding when entitled. PAYG report access requires verified card setup and approved sites; activation is limited to the enabled test flow described above. If a saved report or PDF includes a site that is no longer approved, access is refused and it may disappear from the archive. Generate a new report for the current authorised scope when available. This check also applies when opening a monthly report that automatically selects a saved issued version. An individually approved site report can remain accessible even when an older combined report is refused. Existing stored figures are not rewritten. An administrator who can read billing can review it. Other members ask that person.