CVE-2023-26583
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 GetCurrentPeriod 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 GetCurrentPeriod method of IDAttend IDWeb application versions 3.1.052 and earlier allows remote attackers to execute arbitrary SQL commands without credentials. The vulnerability enables complete compromise of the database including extraction or modification of all stored data.
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 installationSearch system for IDWeb application files, check web server document roots for 'idweb' or 'idattend' directories, or review installed software lists for IDAttend productsAffected if IDAttend IDWeb is present on the system
-
Determine installed IDWeb versionCheck application files for version information (version.txt, about page, or assembly/product metadata within the application directory), or query the application's built-in version endpoint if availableAffected if Installed version is 3.1.052 or earlier
-
Verify GetCurrentPeriod endpoint accessibilityAttempt to access the GetCurrentPeriod method via HTTP request to the IDWeb application (typically at an endpoint containing 'GetCurrentPeriod' or similar), using a test parameter to confirm the method respondsAffected if The GetCurrentPeriod method is reachable without authentication
-
Confirm network exposureReview firewall rules, network configuration, or NAT settings to determine if the IDWeb application is directly accessible from untrusted networks or the internetAffected if IDWeb is exposed to the internet or untrusted networks without authentication barriers
A system is affected if IDAttend IDWeb version 3.1.052 or earlier is installed and the GetCurrentPeriod method is network-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 dataApply the vendor-supplied patch or upgrade to a version beyond 3.1.052. If no patch is available, implement web application firewall rules and temporarily restrict network access to the IDWeb application until a fix is deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-26583 — 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-26583 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