Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2020-36112: SQL Injection in CSE Bookstore 1.0 (pubid parameter)

Published Jan 4, 2021 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS17.6%97th percentile
CISA KEVNoNot listed
In the wildReported477 exploitation records in Mallory
Vendor
Cse Bookstore Project
IdentifiersCVE-2020-36112CWE-89 · Improper Neutralization of Special…

CSE Bookstore 1.0 contains a SQL injection vulnerability in the 'pubid' parameter of bookPerPub.php and cart.php. The application fails to properly sanitize user-supplied input, allowing attackers to perform time-based blind, boolean-based blind, and OR error-based SQL injection attacks. This enables an attacker to execute arbitrary SQL queries 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 an attacker to dump the entire database, potentially exposing sensitive user data, credentials, and other application data. The attacker may also be able to modify or delete data, depending on database permissions.

Mitigation

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

If immediate remediation is not possible, restrict access to the affected scripts, implement web application firewall (WAF) rules to detect and block SQL injection attempts, and monitor database activity for suspicious queries.

Remediation

Patch, then assume compromise.

Update the application to use parameterized queries or prepared statements for all database access involving user-supplied input. Sanitize and validate all input parameters, especially 'pubid', to prevent injection of malicious SQL code. Apply the latest security patches and review code for similar vulnerabilities.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
Cse Bookstore ProjectCse Bookstoreapplication
FAQ

Frequently asked questions

Is CVE-2020-36112 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2020-36112?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2020-36112.
Is there a patch for CVE-2020-36112?
Update the application to use parameterized queries or prepared statements for all database access involving user-supplied input. Sanitize and validate all input parameters, especially 'pubid', to prevent injection of malicious SQL code.
What products are affected by CVE-2020-36112?
Cse Bookstore Project Cse Bookstore.
How severe is CVE-2020-36112?
CVE-2020-36112 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 17.6% (97th 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 signatures1YARA, 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.