CVE-2024-25461
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 · uneditedDirectory Traversal vulnerability in Terrasoft, Creatio Terrasoft CRM v.7.18.4.1532 allows a remote attacker to obtain sensitive information via a crafted request to the terrasoft.axd component.
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 · moderate confidenceA directory traversal vulnerability in the terrasoft.axd handler of Terrasoft CRM v7.18.4.1532 allows remote unauthenticated attackers to access arbitrary files on the server by using '../' path traversal sequences in crafted HTTP requests, potentially exposing sensitive system configuration files and credentials.
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= 7.18.4.1532CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Creatio/Terrasoft CRM versionLocate the version information in the Creatio installation directory, typically in assembly metadata, configuration files, or the About section of the application. Common paths include the web.config file or application binaries.Affected if The installed version is exactly 7.18.4.1532 (exact match per affected version listing)
-
Confirm the terrasoft.axd handler is present and enabledCheck the web server configuration (IIS web.config, Apache config, or the application's handler mappings) for a registration of 'terrasoft.axd' as an HTTP handler.Affected if The terrasoft.axd handler is registered and enabled on the web server
-
Verify unauthenticated access to terrasoft.axdSend a direct HTTP request to the terrasoft.axd endpoint without any authentication credentials. For example: GET /terrasoft.axd or GET /[path]/terrasoft.axdAffected if The handler responds to unauthenticated requests (no login prompt or 401/403 error)
-
Test for path traversal vulnerability (optional - may be disruptive)If authorized, send a crafted request with '../' sequences to attempt directory traversal, such as: GET /terrasoft.axd?file=../../web.configAffected if The application returns file contents from outside the intended directory, confirming the vulnerability exists
You are affected if your Creatio CRM installation is exactly version 7.18.4.1532 AND the terrasoft.axd handler is exposed to unauthenticated users.
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 dataImplement strict input validation on all file path parameters to reject traversal sequences ('../'), restrict the terrasoft.axd handler to authorized users only, and apply principle of least privilege to file system access controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25461 — 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-2024-25461 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