Skip to content
Fencer Intel
high 8.6

CVE-2025-48205 json

The Front End User Registration extension for TYPO3 (sr_feuser_register) allows Insecure Direct Object Reference

published last yr. modified 4mo ago also EUVD-2025-16033 , GHSA-cvgc-mx2w-h3w8

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

The sr_feuser_register extension through 12.4.8 for TYPO3 allows Insecure Direct Object Reference.

Patch / fix

  • packagist sjbr/sr-feuser-register 12.5.0
  • TYPO3 sr feuser register extension 12.5.0

Is CVE-2025-48205 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist sjbr/sr-feuser-register
>=5.1.0, <12.5.0
12.5.0

Affected products

  • TYPO3 sr feuser register extension

Classification

Weakness
  • CWE-425 Direct Request
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.