CVE-2005-3153

UnknownEPSS 1.51%

Last modified

CVE-2005-3153 is a vulnerability of currently unknown severity. login.php in myBloggie 2.1.3 beta and earlier allows remote attackers to bypass a whitelist regular expression and conduct SQL injection attacks via a username parameter with SQL after a null character, which causes the whitelist check to succeed but injects the SQL into a query string, a different vulnerability than CVE-2005-2838. NOTE: it is possible that this is actually a bug in PHP code, in which case this should not be treated as a myBloggie vulnerability.. EPSS estimates a 1.51% chance of exploitation in the next 30 days.

Description

login.php in myBloggie 2.1.3 beta and earlier allows remote attackers to bypass a whitelist regular expression and conduct SQL injection attacks via a username parameter with SQL after a null character, which causes the whitelist check to succeed but injects the SQL into a query string, a different vulnerability than CVE-2005-2838. NOTE: it is possible that this is actually a bug in PHP code, in which case this should not be treated as a myBloggie vulnerability.

Metrics

EPSS Probability
1.51%

71.3th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersions
MyweblandMybloggie2.1.3_beta

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2005-3153?
login.php in myBloggie 2.1.3 beta and earlier allows remote attackers to bypass a whitelist regular expression and conduct SQL injection attacks via a username parameter with SQL after a null character, which causes the whitelist check to succeed but injects the SQL into a query string, a different vulnerability than CVE-2005-2838. NOTE: it is possible that this is actually a bug in PHP code, in which case this should not be treated as a myBloggie vulnerability.
How severe is CVE-2005-3153?
Severity scoring for CVE-2005-3153 is pending analysis. The EPSS model estimates a 1.51% probability of exploitation in the next 30 days.
How do I fix CVE-2005-3153?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2005-3153?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST