Skip to main content
Mallory
HighVulnerability

CVE-2009-2881: SQL Injection in Basilic 1.5.13 idAuthor Parameter

Published Aug 20, 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.2%68th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Artis.Imag
IdentifiersCVE-2009-2881CWE-89 · Improper Neutralization of Special…

Basilic 1.5.13 contains multiple SQL injection vulnerabilities due to insufficient sanitization of the 'idAuthor' parameter in 'index.php' and possibly 'allpubs.php' within the publications/ directory. Remote attackers can exploit these flaws by supplying crafted input to the vulnerable parameter, resulting in the execution of arbitrary SQL commands against the backend database.

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 queries, which can lead to unauthorized data access, data modification, or deletion. Attackers may also leverage the vulnerability to escalate privileges or compromise the underlying system depending on the database configuration and application logic.

Mitigation

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

As an interim measure, implement strict input validation and sanitization for the 'idAuthor' parameter. Employ web application firewalls (WAFs) to detect and block SQL injection attempts. Restrict database user privileges to minimize the impact of a successful attack.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of Basilic where input validation and parameterized queries are properly implemented for all user-supplied input, especially the 'idAuthor' parameter. Review and sanitize all database interactions to prevent SQL injection.

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
Artis.ImagBasilicapplication
FAQ

Frequently asked questions

Is CVE-2009-2881 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-2881 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-2881?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-2881. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2009-2881?
Upgrade to a patched version of Basilic where input validation and parameterized queries are properly implemented for all user-supplied input, especially the 'idAuthor' parameter. Review and sanitize all database interactions to prevent SQL injection.
What products are affected by CVE-2009-2881?
Artis.Imag Basilic.
How severe is CVE-2009-2881?
CVE-2009-2881 has a CVSS v2 score of 7.5 (High) and an EPSS score of 1.2% (68th 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.