Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
9 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
The femanager extension for TYPO3 allows Insecure Direct Object Reference resulting in unauthorized modification of userdata. This issue affects femanager version 6.4.1 and below, 7.0.0 to 7.5.2 and 8.0.0 to 8.3.0.
Recommended action: Upgrade to 8.3.1, 7.5.3 or 6.4.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Insecure Direct Object Reference (IDOR) in the femanager TYPO3 extension allows attackers to view frontend user data via a user parameter in the newAction of the newController.
Recommended action: Upgrade to 8.2.2, 7.4.2, 6.4.1 or 5.5.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The extension fails to check access permissions for the edit user component. An authenticated frontend user can use the vulnerability to either edit data of various frontend users or to delete various frontend user accounts. Another missing access check in the backend module of the extensions allows an authenticated backend user to perform various actions (userLogout, confirmUser, refuseUser and resendUserConfirmation) for any frontend user in the system.
Recommended action: Upgrade to 7.2.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
femanager fails to check access permissions for the invitation component. Depending on the configuration of the plugin, a remote user can create frontend user accounts with access to configured frontend groups.
Recommended action: Upgrade to 7.2.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A missing access check in the InvitationController allows an unauthenticated user to delete all frontend users.
Recommended action: Upgrade to 7.1.0, 6.3.4 or 5.5.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A missing access check in the InvitationController allows an unauthenticated user with a valid invitation link to set the password of all frontend users.
Recommended action: Upgrade to 7.1.0, 6.3.4 or 5.5.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The TYPO3 Extension femanager prior to versions 5.5.2, 6.3.3, and 7.0.1 is vulnerable to broken access control. The usergroup.inList validation can be bypassed resulting in new frontend users created by the extension may be members of groups that are restricted. The vulnerability is only exploitable if the field usergroup is available in the registration form. Versions 5.5.2, 6.3.3, and 7.0.1 contain patches.
Recommended action: Upgrade to 7.0.1, 6.3.3 or 5.5.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The femanager extension before 1.0.9 for TYPO3 allows remote frontend users to modify or delete the records of other frontend users via unspecified vectors.
Recommended action: Upgrade to 1.0.9 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The extension allows by default to upload SVG files when a logged in frontend user uploads a new profile image. This may lead to Cross-Site Scripting, when the uploaded SVG image is used as is on the website. Note: If SVG uploads are required, it is recommended to use the TYPO3 extension svgsanitizer (added to TYPO3 core since versions 9.5.28, 10.4.18 and 11.3.0) to prevent upload of malicious SVG files or to set up a strict Content Security Policy for the destination folder of uploaded images.
Recommended action: Upgrade to 6.3.1 or 5.5.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.