CVE-2014-6292: Medium severity typo3 femanager vulnerability
Published Oct 3, 2014
·Updated
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.
Affected Software
10 affected componentsFixes available
composer/in2code/femanager<1.0.9
1.0.9
In2code Femanager Typo3<=1.0.8
In2code Femanager Typo3=1.0.0
In2code Femanager Typo3=1.0.1
In2code Femanager Typo3=1.0.2
In2code Femanager Typo3=1.0.3
In2code Femanager Typo3=1.0.4
In2code Femanager Typo3=1.0.5
In2code Femanager Typo3=1.0.6
In2code Femanager Typo3=1.0.7
Remediation
Patch Available
Event History
Oct 3, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
May 13, 2022
Advisory Published
via GitHub·01:04 AM
Data Sourced
via GitHub·01:04 AM
DescriptionWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2014-6292?
CVE-2014-6292 is considered a critical vulnerability as it allows remote frontend users to modify or delete records of other users.
2
How do I fix CVE-2014-6292?
To fix CVE-2014-6292, upgrade the femanager extension to version 1.0.9 or later.
3
Who is affected by CVE-2014-6292?
CVE-2014-6292 affects all versions of the femanager extension prior to version 1.0.9 for TYPO3.
4
What could happen if CVE-2014-6292 is exploited?
If exploited, CVE-2014-6292 could allow unauthorized users to access, modify, or delete sensitive user records.
5
Is there a workaround for CVE-2014-6292?
While the best solution is to upgrade the extension, restricting access to frontend features can serve as a temporary workaround for CVE-2014-6292.