dbcve.org
IdwebApplication · Idattend

CVE-2023-26576

HIGH · 7.5 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 3.1.052 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Missing authentication in the SearchStudentsRFID method in IDAttend’s IDWeb application 3.1.052 and earlier allows extraction sensitive student 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 confidence

The IDAttend IDWeb application versions 3.1.052 and earlier contain a missing authentication vulnerability in the SearchStudentsRFID method. Unauthenticated attackers can invoke this method directly to extract sensitive student data without any credentials or session tokens.

MitigationImplement proper authentication and authorization checks on the SearchStudentsRFID method to ensure only authorized users can access student data. This may involve adding the method to authenticated-only endpoints or implementing role-based access controls.

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
IdwebApplication
Affected:<= 3.1.052

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify IDAttend IDWeb installation
    Locate the IDWeb application installation directory and look for version indicators in application files, configuration, or the application's about/help page
    Affected if IDAttend IDWeb is installed and version is 3.1.052 or lower
  2. Determine installed version number
    Check the application's version file, DLL metadata, or the version displayed in the software interface against the affected range <= 3.1.052
    Affected if Installed version is 3.1.052 or any earlier version
  3. Verify SearchStudentsRFID method exposure
    Attempt to access the SearchStudentsRFID endpoint directly via HTTP request without providing any authentication credentials or session tokens
    Affected if The method responds to unauthenticated requests and returns student data
  4. Check endpoint accessibility
    Use a web proxy or curl to send a request to the SearchStudentsRFID endpoint URL and observe whether the application returns data without requiring login
    Affected if The endpoint is reachable without authentication and exposes student information

If IDAttend IDWeb version 3.1.052 or lower is installed AND the SearchStudentsRFID method is accessible without authentication, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 3.1.052
Interim mitigation

Implement proper authentication and authorization checks on the SearchStudentsRFID method to ensure only authorized users can access student data. This may involve adding the method to authenticated-only endpoints or implementing role-based access controls.

Recommended fix Moderate confidence

Contact IDAttend for the specific fixed version (version after 3.1.052)

  1. 1. Identify the current version of IDAttend's IDWeb application in use
  2. 2. Contact IDAttend vendor directly to obtain the latest secure version that includes the authentication fix for CVE-2023-26576
  3. 3. Request specific version number that addresses the missing authentication in SearchStudentsRFID method
  4. 4. Plan and schedule the upgrade during a maintenance window
  5. 5. Back up current configuration and database before upgrading
  6. 6. Apply the upgrade following vendor-provided installation instructions
  7. 7. Verify the upgrade was successful and the SearchStudentsRFID method now requires authentication
Caveat Check with vendor for any configuration changes or migration requirements when upgrading from 3.1.052

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Idweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26576 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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