in2code/femanager vulnerabilities
Modern TYPO3 Frontend User Registration.
- Registry
- Composer
- Latest
- 13.4.1
- License
- GPL-2.0-or-later
9 known advisories
The latest version, 13.4.1, is not affected by any of them. Projects on older versions may be.
composer require in2code/femanager:^13.4.1Is your project on an affected in2code/femanager?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for in2code/femanager
Femanager extension for TYPO3 allows Insecure Direct Object Reference
- Affected
- <6.4.2 · >=7.0.0 <7.5.3 · >=8.0.0 <8.3.1
- Fixed in
- 6.4.2, 7.5.3, 8.3.1
The femanager TYPO3 extension allows Insecure Direct Object Reference
- Affected
- >=8.0.0 <8.2.2 · >=7.0.0 <7.4.2 · >=6.0.0 <6.4.1 · >=5.5.0 <5.5.5
- Fixed in
- 5.5.5, 6.4.1, 7.4.2, 8.2.2
Broken Access Control in extension "femanager"
- Affected
- >=7.0.0 <7.2.3
- Fixed in
- 7.2.3
TYPO3 extension femanager Broken Access Control vulnerability
- Affected
- >=7.0.0 <7.2.2
- Fixed in
- 7.2.2
Broken Access Control in 3rd party TYPO3 extension "femanager"
- Affected
- <5.5.3 · >=6.0.0 <6.3.4 · >=7.0.0 <7.1.0
- Fixed in
- 5.5.3, 6.3.4, 7.1.0
Broken Access Control in 3rd party TYPO3 extension "femanager"
- Affected
- <5.5.3 · >=6.0.0 <6.3.4 · >=7.0.0 <7.1.0
- Fixed in
- 5.5.3, 6.3.4, 7.1.0
TYPO3 Extension femanager vulnerable to Broken Access Control
- Affected
- >=7.0.0 <7.0.1 · >=6.0.0 <6.3.3 · <5.5.2
- Fixed in
- 5.5.2, 6.3.3, 7.0.1
TYPO3 femanager extension allows remote frontend users to modify or delete records of other frontend users
- Affected
- <1.0.9
- Fixed in
- 1.0.9
Cross-site Scripting in the femanager TYPO3 extension
- Affected
- <5.5.1 · >=6.0.0 <6.3.1
- Fixed in
- 5.5.1, 6.3.1
Is your in2code/femanager version vulnerable?
- in2code/femanager 13.4No known advisories in 13.4.1
- in2code/femanager 13.3No known advisories in 13.3.6
- in2code/femanager 13.2No known advisories in 13.2.1
- in2code/femanager 13.1No known advisories in 13.1.0
- in2code/femanager 13.0No known advisories in 13.0.0
- in2code/femanager 8.4No known advisories in 8.4.2
- in2code/femanager 8.3No known advisories in 8.3.3
- in2code/femanager 8.21 advisory in 8.2.2
- in2code/femanager 8.12 advisories in 8.1.0
- in2code/femanager 8.02 advisories in 8.0.1
- in2code/femanager 7.5No known advisories in 7.5.5
- in2code/femanager 7.41 advisory in 7.4.2
- in2code/femanager 7.32 advisories in 7.3.0
- in2code/femanager 7.22 advisories in 7.2.3
- in2code/femanager 7.14 advisories in 7.1.1
- in2code/femanager 7.06 advisories in 7.0.1
Which of your client projects still run an old in2code/femanager?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.