Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2008-2646: XSS in meBiblio 0.4.7

Published Jun 10, 2008 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.3Medium · v2
EPSS1.4%74th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Mebiblio
IdentifiersCVE-2008-2646CWE-79 · Improper Neutralization of Input…

Multiple cross-site scripting (XSS) vulnerabilities exist in meBiblio 0.4.7. The vulnerabilities are present in the handling of user-supplied input to the 'sql' parameter in dbadd.inc.php, the 'InsertJournal' parameter in add_journal_mask.inc.php, the 'InsertBibliography' parameter in insert_mask.inc.php, and the 'LabelYear' parameter in search_mask.inc.php. These parameters are not properly sanitized, allowing attackers to inject arbitrary web script or HTML.

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 JavaScript in the context of the victim's browser session. This can lead to session hijacking, credential theft, or other attacks leveraging the trust relationship between the user and the application.

Mitigation

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

Restrict access to the application to trusted users, employ web application firewalls to filter malicious input, and use browser security features such as Content Security Policy (CSP) to reduce the impact of XSS. Regularly audit code for input validation issues.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of meBiblio where input validation and output encoding are properly implemented for all user-supplied parameters. If no official patch is available, manually sanitize and encode all user input before rendering it in the browser.

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
MebiblioMebiblioapplication
FAQ

Frequently asked questions

Is CVE-2008-2646 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-2646 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-2646?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2008-2646.
Is there a patch for CVE-2008-2646?
Upgrade to a patched version of meBiblio where input validation and output encoding are properly implemented for all user-supplied parameters. If no official patch is available, manually sanitize and encode all user input before rendering it in the browser.
What products are affected by CVE-2008-2646?
Mebiblio.
How severe is CVE-2008-2646?
CVE-2008-2646 has a CVSS v2 score of 4.3 (Medium) and an EPSS score of 1.4% (74th 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.