CVE-2024-24525
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 · uneditedAn issue in EpointWebBuilder 5.1.0-sp1, 5.2.1-sp1, 5.4.1 and 5.4.2 allows a remote attacker to execute arbitrary code via the infoid parameter of the URL.
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 confidenceEpointWebBuilder versions 5.1.0-sp1 through 5.4.2 contain a critical remote code execution (RCE) vulnerability where the 'infoid' URL parameter is not properly sanitized, allowing unauthenticated remote attackers to inject and execute arbitrary system commands on the hosting server.
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= 5.1.0= 5.2.1= 5.4.1= 5.4.2CVSS 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 EpointWebBuilder installation versionLocate the version information in the application by checking the login page, About page, or version file typically found in the web root or admin panel. Compare your installed version to the affected range: 5.1.0-sp1 through 5.4.2.Affected if The installed version falls within 5.1.0-sp1, 5.2.1, 5.4.1, or 5.4.2
-
Confirm web application accessibilityDetermine if the EpointWebBuilder web interface is publicly accessible by attempting to access the application URL or reviewing network firewall rules and web server configuration.Affected if The application is accessible over HTTP/HTTPS without authentication restrictions
-
Identify exposed 'infoid' parameter endpointScan the web application for endpoints that accept an 'infoid' parameter, such as URLs matching patterns like /index.php?mod=xxx&infoid=VALUE or similar. Review web server access logs for requests containing 'infoid' as a query parameter.Affected if Endpoints accepting the 'infoid' parameter are publicly accessible without authentication
-
Review web server access logs for exploitation attemptsSearch web server access logs (typically Apache access.log, Nginx access.log, or IIS HTTP logs) for requests containing 'infoid' parameter with suspicious patterns such as command injection operators (| ; $() `` wget curl), common RCE payloads, or shell script references.Affected if Log entries show 'infoid' parameter values containing command injection payloads or unusual system commands
-
Check for evidence of remote command executionExamine application and system logs for signs of successful command execution, including unexpected processes, newly created files in web-accessible directories, or unusual cron/scheduled tasks. Review web server error logs for injection attempts.Affected if Logs or file system show evidence of commands being executed by the web server process outside normal application behavior
You are affected if EpointWebBuilder version 5.1.0-sp1 through 5.4.2 is installed and the application with its 'infoid' parameter is accessible without authentication, or if logs show exploitation attempts targeting the infoid parameter.
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 vendor patches immediately if available; otherwise implement strict input validation and sanitization on the infoid parameter, deploy WAF rules to block malicious payloads, and consider temporarily restricting access to affected endpoints until a permanent fix is implemented.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24525 — 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-24525 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