IdwebApplication · Idattend

CVE-2023-26574

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 SearchStudents 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

IDAttend's IDWeb application 3.1.052 and earlier lacks authentication enforcement on the SearchStudents method, allowing any unauthenticated user to invoke this function and extract sensitive student data such as names, contact information, enrollment details, or other PII stored in the student database.

MitigationImplement authentication and authorization checks on the SearchStudents method to ensure only authenticated and authorized users can access student data; consider conducting a broader security audit to identify other unprotected endpoints.

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 IDWeb application version
    Locate the IDWeb application installation and check the version information, typically found in the application metadata, about page, or version file within the installation directory
    Affected if The installed version is 3.1.052 or any earlier version
  2. Locate the SearchStudents method endpoint
    Identify the URL path or API endpoint that corresponds to the SearchStudents method within the IDWeb application, typically found in the application's web configuration or API documentation
    Affected if The SearchStudents endpoint exists and is accessible within the application
  3. Test unauthenticated access to SearchStudents
    Attempt to invoke the SearchStudents method via HTTP request without providing any authentication credentials (cookies, tokens, or session identifiers)
    Affected if The request returns student data or valid response without requiring authentication
  4. Verify authentication enforcement on the endpoint
    Review the application's security configuration, web.xml, or access control settings to confirm whether authentication is required for the SearchStudents method
    Affected if No authentication requirement is configured or enforced for the SearchStudents endpoint

The environment is affected if the IDWeb version is 3.1.052 or earlier AND the SearchStudents method can be accessed without providing valid authentication credentials.

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.

From vendor data
Upgrade available Upgrade to a release after 3.1.052
Interim mitigation

Implement authentication and authorization checks on the SearchStudents method to ensure only authenticated and authorized users can access student data; consider conducting a broader security audit to identify other unprotected endpoints.

Fix this in Idweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26574 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-26574 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