Quick answers
- Is CVE-2023-50459 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2023-50459 being exploited in the wild.
- How severe is CVE-2023-50459?
- Medium severity, with a CVSS score of 5.4, published 14 September 2026.
- Which products and versions are affected?
- In2code Femanager 7.0.0 to 7.2.2; in2code/femanager (Packagist) ECOSYSTEM:introduced=7.0.0,fixed=7.2.3.
- Is there a fix for CVE-2023-50459?
- Yes. in2code/femanager (Packagist): upgrade to 7.2.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2023-50459 attacked?
- It is attacked over the network.
- Am I affected by CVE-2023-50459?
- Check whether you run In2code Femanager or in2code/femanager (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- in2code/femanager (Packagist): upgrade to 7.2.3 or later
composer require in2code/femanager:^7.2.3
Technical details
The vulnerability is a broken access control (CWE-284) flaw in the femanager extension's edit user component. An authenticated frontend user can exploit insufficient permission checks to modify arbitrary frontend user data or delete user accounts. The vulnerability affects versions 7.0.0 through 7.2.2 and is exploitable over the network by any authenticated frontend user without user interaction required. A similar access control flaw in the backend module allows authenticated backend users to perform unauthorized actions on any frontend user. The issue has been patched in version 7.2.3.
Affected products
- in2code femanager 7.0.0 to 7.2.2
Identifiers
- CVE-2023-50459
- GHSA-4xp5-hr35-84cx
Timeline
- 2023-12-13: disclosed
- 2023-12-13: patched: Version 7.2.3 released