CVE-2005-3153: n/a vulnerability

CVE-2005-3153: login.php in myBloggie 2.1.3 beta and earlier allows remote attackers to bypass a whitelist regular express...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 23:01 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy web application login flaw. The source description says myBloggie login.php could let a remote attacker bypass input filtering and trigger SQL injection through the username field, potentially bypassing login. Exposure matters mainly if an organization still runs myBloggie 2.1.3 beta or earlier. Likely limited to legacy internet-facing myBloggie installations, especially version 2.1.3 beta or earlier. The provided affected metadata is incomplete and lists no CPEs, so inventory confirmation is required. Treat as urgent only where legacy myBloggie is still deployed, especially on the internet. Otherwise, prioritize inventory cleanup and legacy application retirement. Mitigation focus: Identify and retire any myBloggie 2.1.3 beta or earlier deployments.; Check vendor or project guidance before applying any assumed patch.; Restrict public access to legacy myBloggie instances pending remediation..

Prepared: Jun 29, 2026, 17:44 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2005-3153 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Oct 5, 2005, 04:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.