Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2008-6623: SQL Injection in WEBBDOMAIN Post Card getin.php

Published Apr 6, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS1.0%64th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Webbdomain
IdentifiersCVE-2008-6623CWE-89 · Improper Neutralization of Special…

A SQL injection vulnerability exists in WEBBDOMAIN Post Card (Web Postcards) version 1.02 and earlier, specifically in the getin.php script. The vulnerability is due to insufficient sanitization of user-supplied input in the 'username' parameter, allowing attackers to inject arbitrary SQL commands.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary SQL commands against the application's backend database. This can lead to unauthorized data access, data modification, or potentially full compromise of the application and underlying server.

Mitigation

If you can’t patch tonight, do this now.

As an immediate mitigation, implement input validation and escaping for the 'username' parameter in getin.php. Use prepared statements or parameterized queries to prevent SQL injection. Restrict database user privileges to minimize impact if exploitation occurs.

Remediation

Patch, then assume compromise.

Upgrade to a version of WEBBDOMAIN Post Card where input validation and parameterized queries are properly implemented in getin.php. Ensure all user-supplied input is sanitized before use in SQL statements.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WebbdomainPost Cardapplication
FAQ

Frequently asked questions

Is CVE-2008-6623 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-6623 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-6623?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2008-6623.
Is there a patch for CVE-2008-6623?
Upgrade to a version of WEBBDOMAIN Post Card where input validation and parameterized queries are properly implemented in getin.php. Ensure all user-supplied input is sanitized before use in SQL statements.
What products are affected by CVE-2008-6623?
Webbdomain Post Card.
How severe is CVE-2008-6623?
CVE-2008-6623 has a CVSS v2 score of 7.5 (High) and an EPSS score of 1.0% (64th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.