CVE-2023-26572
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 · uneditedUnauthenticated SQL injection in the GetExcursionList method in IDAttend’s IDWeb application 3.1.052 and earlier allows extraction or modification of all data by unauthenticated attackers.
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 confidenceAn unauthenticated SQL injection vulnerability exists in the GetExcursionList method of IDAttend IDWeb application versions 3.1.052 and earlier. Attackers can exploit this flaw via specially crafted HTTP requests to inject malicious SQL statements, enabling complete extraction or modification of the database contents without any authentication credentials.
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 data<= 3.1.052CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Identify if IDAttend IDWeb is installedReview your web server's installed applications or software inventory for IDAttend IDWeb. Check for directories or services named 'IDWeb', 'IDAttend', or related web application paths.Affected if IDAttend IDWeb is present in your environment
-
Determine the installed versionLocate the version information for the IDWeb application. This is typically found in the application header, an about page, a configuration file, or the assembly/dll version metadata if it's a .NET application. Compare your version to 3.1.052.Affected if The installed version is 3.1.052 or any earlier version
-
Locate the GetExcursionList endpointIdentify if the GetExcursionList method is exposed as a web endpoint. Check application routing configurations, published web services, or API mappings for URLs containing 'GetExcursionList' or similar excursion-related paths.Affected if The GetExcursionList endpoint is accessible via HTTP
-
Verify unauthenticated access is possibleAttempt to access the GetExcursionList endpoint without providing any authentication credentials. Observe whether the application returns a valid response or an error rather than redirecting to a login page or returning an authentication error.Affected if The endpoint responds to unauthenticated requests without requiring login credentials
Your environment is affected if IDAttend IDWeb version 3.1.052 or earlier is installed and the GetExcursionList endpoint is accessible without authentication.
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 dataUpgrade IDWeb to a version newer than 3.1.052 and implement parameterized queries or prepared statements in the GetExcursionList method to prevent SQL injection. Apply input validation and least-privilege database accounts as defense-in-depth measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26572 — 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-2023-26572 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