Skip to main content
Mallory
HighVulnerability

CVE-2007-4956: SQL Injection in KwsPHP 1.0

Published Sep 18, 2007 · 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
EPSS3.5%90th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Kwsphp
IdentifiersCVE-2007-4956CWE-89 · Improper Neutralization of Special…

KwsPHP 1.0 contains multiple SQL injection vulnerabilities. Specifically, the pseudo parameter in login.php, the id parameter in index.php when performing a carnet editer action in the Member_Space (espace_membre) module, and the typenav parameter in index.php during a browser aff action in the stats module are all susceptible to SQL injection. These flaws allow remote attackers to inject arbitrary SQL commands into database queries executed by the application.

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 deletion, and potentially full compromise of the application and underlying system if further chained with other vulnerabilities.

Mitigation

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

As an immediate mitigation, deploy a web application firewall (WAF) to filter malicious input, and restrict database user privileges to limit the impact of a successful injection. Additionally, ensure that all user-supplied input is validated and sanitized before being used in SQL queries.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of KwsPHP that properly sanitizes and parameterizes all user-supplied input before using it in SQL queries. If no official patch is available, manually review the affected scripts and implement input validation and prepared statements to prevent SQL injection.

Public exploits

Exploits

No validated public exploits yet. Hidden: 3 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
KwsphpKwsphpapplication
FAQ

Frequently asked questions

Is CVE-2007-4956 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2007-4956 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2007-4956?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2007-4956. 3 candidate exploit records are not yet analyzed.
Is there a patch for CVE-2007-4956?
Upgrade to a patched version of KwsPHP that properly sanitizes and parameterizes all user-supplied input before using it in SQL queries. If no official patch is available, manually review the affected scripts and implement input validation and prepared statements to prevent SQL injection.
What products are affected by CVE-2007-4956?
Kwsphp.
How severe is CVE-2007-4956?
CVE-2007-4956 has a CVSS v2 score of 7.5 (High) and an EPSS score of 3.5% (90th 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.