CVE-2023-26582
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 GetExcursionDetails 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 · high confidenceUnauthenticated SQL injection vulnerability in the GetExcursionDetails method of IDAttend IDWeb application 3.1.052 and earlier allows remote attackers to execute arbitrary SQL commands without authentication, enabling complete data extraction or modification of the database.
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 IDAttend IDWeb installationCheck for IDAttend IDWeb application files on the server, typically found in the web root directory. Look for application files, DLLs, or configuration files that indicate IDWeb is installed.Affected if IDAttend IDWeb is installed on the system
-
Determine IDWeb versionLocate version information in the application files, typically in assembly info, a version file, or the application configuration. Check for a file named similar to version.txt, or inspect DLL metadata if available.Affected if The installed version is 3.1.052 or any earlier version
-
Verify GetExcursionDetails endpoint existsCheck the application web routes or source code for the GetExcursionDetails method. This is typically exposed via a web service endpoint or API controller. Look for references to 'GetExcursionDetails' in the codebase or configuration.Affected if The GetExcursionDetails method is present and exposed as a web endpoint
-
Confirm application is network-accessibleVerify the IDWeb application is accessible over the network (HTTP/HTTPS). Since this is an unauthenticated SQL injection, the attacker would need network access to the application.Affected if The IDWeb application is accessible from network locations without authentication
A user is affected if IDAttend IDWeb version 3.1.052 or earlier is installed and the GetExcursionDetails web endpoint is exposed to network access.
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 dataApply vendor patch for IDWeb 3.1.052 or later; until patched, consider network-level restrictions to the application and implement web application firewall rules to detect/block SQL injection patterns.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26582 — 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-26582 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