Is symbiote/silverstripe-queuedjobs 3.0 vulnerable?

Composer · 3 releases from 3.0.0 to 3.0.2 · latest symbiote/silverstripe-queuedjobs is 6.2.4 · checked 18 Nov 2026

No known advisories in the last release

symbiote/silverstripe-queuedjobs 3.0.2, the last 3.0 release, has no known advisories. 1 advisory affects earlier 3.0.x releases, so update to 3.0.2.

Update within 3.0:composer require symbiote/silverstripe-queuedjobs:^3.0.2

Is your project on an affected symbiote/silverstripe-queuedjobs?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 3.0.x, affecting earlier releases

  • MediumCVE-2021-27938GHSA-xgpf-p52j-pf7m24 Mar 2021

    XSS in CreateQueuedJobTask

    Affected
    >=3.0.0 <3.0.2 · >=3.1.0 <3.1.4 · >=4.0.0 <4.0.7 · >=4.1.0 <4.1.2 · >=4.2.0 <4.2.4 · >=4.3.0 <4.3.3 · >=4.4.0 <4.4.3 · >=4.5.0 <4.5.1 · >=4.6.0 <4.6.4
    Fixed in
    3.0.2, 3.1.4, 4.0.7, 4.1.2, 4.2.4, 4.3.3, 4.4.3, 4.5.1, 4.6.4

Every symbiote/silverstripe-queuedjobs 3.0.x release

Affected: 3.0.0 to 3.0.1. 3.0.2 is not affected. Latest symbiote/silverstripe-queuedjobs: 6.2.4.

VersionKnown advisories
symbiote/silverstripe-queuedjobs 3.0.2None
symbiote/silverstripe-queuedjobs 3.0.1CVE-2021-27938
symbiote/silverstripe-queuedjobs 3.0.0CVE-2021-27938

Which of your client projects are still on symbiote/silverstripe-queuedjobs 3.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact symbiote/silverstripe-queuedjobs version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other symbiote/silverstripe-queuedjobs versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.