VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

sjbr/sr-feuser-register: vulnerability history, versions and safety

sjbr/sr-feuser-register is a package in the Packagist ecosystem. Vulert records 4 vulnerabilities for it across 26 releases, from May 2022 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H2 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sjbr/sr-feuser-register vulnerabilities

Vulert verdict on sjbr/sr-feuser-register i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 21 May 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 4 vulnerabilities on record across 3 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 4 over 3 years · 0 in the last year i
  • Latest disclosure 21 May 2025 i
  • Highest CVSS 10.0 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for sjbr/sr-feuser-register, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
6.0.2 C1 H1 Yes Details →
6.0.1 C1 H1 Yes Details →
6.0.0 C1 H1 Yes Details →
5.1.2 C1 H1 Yes Details →
5.1.1 C1 H1 Yes Details →
5.1.0 C1 H1 Yes Details →
v12.4.8 C1 H1 Yes Details →
v12.4.7 C1 H1 Yes Details →
v12.4.6 C1 H1 Yes Details →
v12.4.5 C1 H1 Yes Details →
v12.4.4 C1 H1 Yes Details →
v12.4.3 C1 H1 Yes Details →
v12.4.2 C1 H1 Yes Details →
v12.4.1 C1 H1 Yes Details →
v11.5.5 C1 H1 Yes Details →
v11.5.4 C1 H1 Yes Details →
v11.5.3 C1 H1 Yes Details →
v11.5.2 C1 H1 Yes Details →
v11.5.1 C1 H1 Yes Details →
v11.5.0 C1 H1 Yes Details →
v10.4.0 C1 H1 Yes Details →
v7.0.5 C1 H1 Yes Details →
v7.0.4 C1 H1 Yes Details →
v7.0.3 C1 H1 Yes Details →
v7.0.2 C1 H1 Yes Details →
v7.0.0 C1 H1 Yes Details →

Newest 26 of 26 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sjbr/sr-feuser-register

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-48200: Remote Code Execution in sjbr/sr-feuser-register Extension for TYPO3 10.0 critical 12.5.0 21 May 2025
CVE-2009-1264: Frontend User Registration Extension for TYPO3 Vulnerability - Inadequate Access Rights Verification 8.7 high 2.5.21 02 May 2022
CVE-2025-48205: Insecure Direct Object Reference in sjbr/sr-feuser-register Extension for TYPO3 8.6 high 12.5.0 21 May 2025
CVE-2012-5890: sjbr/sr-feuser-register - Remote User Credentials Exposure Vulnerability 6.6 medium 2.6.2 17 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sjbr/sr-feuser-register

Is sjbr/sr-feuser-register safe to use?

Vulert records 4 vulnerabilities for sjbr/sr-feuser-register in Packagist: 1 critical, 2 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does sjbr/sr-feuser-register have?

4 vulnerabilities are recorded for sjbr/sr-feuser-register in the Packagist ecosystem: 1 critical, 2 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sjbr/sr-feuser-register vulnerabilities disclosed?

0 vulnerabilities were recorded for sjbr/sr-feuser-register in the last 12 months, and the oldest entry in this database dates to 02 May 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sjbr/sr-feuser-register are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor sjbr/sr-feuser-register for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sjbr/sr-feuser-register version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.