CVE-2022-2726
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 · uneditedA vulnerability classified as critical has been found in SEMCMS. This affects an unknown part of the file Ant_Check.php. The manipulation of the argument DID leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-205839.
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 · moderate confidenceCritical SQL injection vulnerability in SEMCMS Ant_Check.php where the DID parameter is not properly sanitized, allowing remote attackers to inject arbitrary SQL queries. The exploit is publicly available, increasing risk.
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 dataall versionsCVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SemCMS installationSearch the web root for SemCMS files, directories, or identifiers (look for 'semcms', 'SEMCMS', or typical SemCMS folder structures like 'SEMCMS_Include').Affected if SemCMS is present in the environment.
-
Locate Ant_Check.phpFind the file Ant_Check.php within the SemCMS installation directory structure, typically in the main or admin folder of the web root.Affected if Ant_Check.php exists in the SemCMS installation.
-
Verify DID parameter handlingExamine Ant_Check.php source code and search for the DID parameter usage. Look for code that retrieves DID from $_GET, $_POST, or $_REQUEST without sanitization.Affected if The code reads the DID parameter from user input (GET/POST/REQUEST) in Ant_Check.php.
-
Check for SQL injection vulnerabilityReview the code around the DID parameter usage. Look for direct string concatenation in SQL queries without using prepared statements, parameterized queries, or escaping functions.Affected if The DID parameter is used directly in SQL queries without sanitization or parameter binding.
-
Assess exposureDetermine if Ant_Check.php is accessible via the web (not protected by authentication, .htaccess restrictions, or network filters). Check if the endpoint accepts unauthenticated requests.Affected if The vulnerable endpoint is reachable without authentication or additional access controls.
If SemCMS is installed, Ant_Check.php processes the DID parameter from user input, and the endpoint is accessible, the environment is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediate remediation requires implementing parameterized queries or prepared statements for the DID parameter in Ant_Check.php, plus conducting a broader code review to identify similar injection points across the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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