dbcve.org
212cafeboardApplication · 212cafe

CVE-2007-0549

MEDIUM · 6.8 CVSS v2.0 Published 2007-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting (XSS) vulnerability in list3.php in 212cafeBoard 6.30 Beta allows remote attackers to inject arbitrary web script or HTML via the user parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Classic reflected XSS vulnerability in 212cafeBoard 6.30 Beta's list3.php script. The 'user' parameter accepts unsanitized user input and reflects it back in the HTTP response without proper output encoding, allowing injection of arbitrary JavaScript or HTML.

MitigationImplement proper input validation and output encoding/escaping for the 'user' parameter in list3.php. Use context-appropriate encoding (HTML entity encoding for HTML body context) or employ a web application firewall as a temporary measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
212cafeboardApplication
Affected:= 6.30_beta

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm 212cafeboard installation and version
    Inspect your web application directory for the presence of 212cafeboard files and check version files or headers to determine if version 6.30_beta is installed
    Affected if 212cafeboard version 6.30_beta is present on the server
  2. Locate list3.php script
    Search the web application directory for the file list3.php which contains the vulnerable code
    Affected if list3.php exists in the web application root or subdirectories
  3. Inspect 'user' parameter handling in list3.php
    Review the source code of list3.php to verify whether the 'user' parameter from the HTTP request is used in the response without proper output encoding or HTML entity escaping
    Affected if The 'user' parameter value is directly echoed back in the HTTP response without sanitization or encoding

A user is affected if 212cafeboard 6.30_beta is installed and list3.php contains the vulnerable code that reflects the 'user' parameter without output encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding/escaping for the 'user' parameter in list3.php. Use context-appropriate encoding (HTML entity encoding for HTML body context) or employ a web application firewall as a temporary measure.

Fix this in 212cafeboard Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0549 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0549 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data