What is the vulnerability ID for this weak password requirements issue in the GitHub repository thorsten/phpmyfaq?

The vulnerability ID for this weak password requirements issue in the GitHub repository thorsten/phpmyfaq is CVE-2023-0307.

What is the severity of the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq?

The severity of the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq is critical (severity value: 9.8).

How can I fix the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq?

To fix the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq, update to version 3.1.10 or later.

Where can I find more information about the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq?

You can find more information about the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq in the following references: [Link 1](https://github.com/thorsten/phpmyfaq/commit/8beed2fca5b0b82c6ba866d0ffd286d0c1fbf596) and [Link 2](https://huntr.dev/bounties/fac01e9f-e3e5-4985-94ad-59a76485f215).

What is the Common Weakness Enumeration (CWE) ID for this weak password requirements vulnerability?

The Common Weakness Enumeration (CWE) ID for this weak password requirements vulnerability is CWE-521.

Vulnerability/
CVE-2023-0307

critical

9.8

CWE

521

15/1/2023

2/8/2024

CVE-2023-0307: Weak Password Requirements in thorsten/phpmyfaq

First published: Sun Jan 15 2023(Updated: )

Weak Password Requirements in GitHub repository thorsten/phpmyfaq prior to 3.1.10.

Credit: security@huntr.dev

Affected Software	Affected Version	How to fix
Phpmyfaq Phpmyfaq	<3.1.10

Remedy

https://github.com/thorsten/phpmyfaq/commit/8beed2fca5b0b82c6ba866d0ffd286d0c1fbf596

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the vulnerability ID for this weak password requirements issue in the GitHub repository thorsten/phpmyfaq?
The vulnerability ID for this weak password requirements issue in the GitHub repository thorsten/phpmyfaq is CVE-2023-0307.
What is the severity of the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq?
The severity of the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq is critical (severity value: 9.8).
How can I fix the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq?
To fix the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq, update to version 3.1.10 or later.
Where can I find more information about the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq?
You can find more information about the weak password requirements vulnerability in the GitHub repository thorsten/phpmyfaq in the following references: [Link 1](https://github.com/thorsten/phpmyfaq/commit/8beed2fca5b0b82c6ba866d0ffd286d0c1fbf596) and [Link 2](https://huntr.dev/bounties/fac01e9f-e3e5-4985-94ad-59a76485f215).
What is the Common Weakness Enumeration (CWE) ID for this weak password requirements vulnerability?
The Common Weakness Enumeration (CWE) ID for this weak password requirements vulnerability is CWE-521.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/remedy
agent/title
agent/weakness
agent/author
agent/last-modified-date
agent/tags
agent/event
agent/description
agent/first-publish-date
vendor/phpmyfaq
canonical/phpmyfaq phpmyfaq

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.