CVE-2025-0929
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 · uneditedSQL injection vulnerability in TeamCal Neo, version 3.8.2. This could allow an attacker to retrieve, update and delete all database information by injecting a malicious SQL statement via the ‘abs’ parameter in ‘/teamcal/src/index.php’.
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 confidenceSQL injection vulnerability in TeamCal Neo v3.8.2 allows remote attackers to execute arbitrary SQL commands via the 'abs' parameter in /teamcal/src/index.php, enabling complete database compromise including unauthorized read, write, and delete operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 TeamCal Neo installation and versionLocate the TeamCal Neo installation directory and check for version information, typically in a version file, README, or the application header. Common paths include /teamcal/ or the web root where TeamCal Neo is deployed.Affected if The installed version is exactly 3.8.2 (the only version explicitly listed as affected).
-
Verify affected file existsConfirm the presence of /teamcal/src/index.php in the web application directory. This file contains the vulnerable code that processes the 'abs' parameter.Affected if The file /teamcal/src/index.php exists in the installation, indicating the vulnerable code path is present.
-
Check if 'abs' parameter handling is presentExamine the index.php file for code that retrieves and uses the 'abs' parameter from user input (typically via $_GET or $_REQUEST) without sanitization. Search for patterns like $_REQUEST['abs'] or $_GET['abs'] being used in SQL queries.Affected if The code directly incorporates the 'abs' parameter into SQL queries without parameterized queries or input sanitization.
-
Test parameter exposureDetermine if the application is accessible via HTTP and if the index.php page processes the 'abs' parameter. Attempt a benign test by submitting a simple value (e.g., ?abs=1) to confirm the parameter is accepted and processed.Affected if The application accepts and processes the 'abs' parameter without validation, making the SQL injection reachable.
A defender is affected if they are running TeamCal Neo version 3.8.2 with the /teamcal/src/index.php file present and the 'abs' parameter accessible and used in unsanitized SQL queries.
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 to a patched version of TeamCal Neo beyond 3.8.2; alternatively, implement prepared statements/parameterized queries or input validation on the 'abs' parameter as an interim workaround.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0929 — 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-2025-0929 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