CVE-2025-48200
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe sr_feuser_register extension through 12.4.8 for TYPO3 allows Remote Code Execution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe sr_feuser_register TYPO3 extension through version 12.4.8 contains a vulnerability allowing remote attackers to execute arbitrary code on the affected TYPO3 system, likely through improper input handling in user registration functionality.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if sr_feuser_register extension is installedIn TYPO3 backend, go to Admin Tools > Extensions > List view and search for 'sr_feuser_register', or run CLI command: typo3cms extension:list | grep sr_feuser_registerAffected if The extension appears in the list of installed extensions
-
Determine the installed version of sr_feuser_registerIn the Extensions list view, note the version number displayed next to sr_feuser_register, or run: typo3cms extension:list | grep -i sr_feuser_registerAffected if The version number is 12.4.8 or lower (versions through 12.4.8 are affected)
-
Verify the extension is activated on your siteCheck the TYPO3 extension manager configuration for sr_feuser_register status, or inspect the file ext_localconf.php in the extension directory for active configurationAffected if The extension is loaded and active in the TYPO3 system
-
Confirm frontend user registration is enabledCheck TYPO3 backend: Go to Web > Template > Constant Editor > Plugin > sr_feuser_register, or inspect the TypoScript setup for plugin.tx_srfeuserregister.settingsAffected if The registration plugin is configured and enabled on the site
-
Review web server logs for suspicious registration requestsExamine access logs and TYPO3 logs (typo3temp/var/log/) for unusual POST requests to user registration forms that may indicate exploitation attemptsAffected if Logs show anomalous requests with suspicious input patterns to registration endpoints
You are affected if the sr_feuser_register extension is installed, active, and running at version 12.4.8 or lower with user registration enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate sr_feuser_register to the latest patched version beyond 12.4.8, or if unavailable, disable and remove the extension until a fix is released.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48200 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data