CVE-2005-1949
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 · uneditedThe eping_validaddr function in functions.php for the ePing plugin for e107 portal allows remote attackers to execute arbitrary commands via shell metacharacters after a valid argument to the eping_host parameter.
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 confidenceThe ePing plugin for e107 contains a command injection vulnerability in the eping_validaddr function in functions.php. Attackers can inject arbitrary shell commands via the eping_host parameter by appending shell metacharacters after a valid hostname argument, allowing remote code execution.
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 dataall versionsCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 if e107 CMS is installedCheck for the presence of e107's main configuration file (e107_config.php or similar) in the web root directory, or look for e107-specific directories and files.Affected if e107 CMS is present on the system
-
Locate the ePing pluginSearch for the ePing plugin directory, typically found under e107_plugins/ in the e107 installation path. Look for a folder named 'eping' or similar.Affected if The ePing plugin directory exists in the e107 installation
-
Find the vulnerable functions.php fileWithin the ePing plugin directory, locate functions.php and verify the presence of the eping_validaddr function.Affected if The functions.php file contains the eping_validaddr function definition
-
Inspect the eping_validaddr function for command injectionOpen functions.php and examine the eping_validaddr function body. Look for instances where the eping_host parameter is passed directly to shell execution functions such as exec(), shell_exec(), passthru(), or system() without proper sanitization or validation.Affected if The eping_host parameter is passed to a shell execution function without sanitizing shell metacharacters
-
Verify the eping_host parameter is exposedCheck if the ePing plugin exposes a web interface that accepts the eping_host parameter (typically via GET or POST request). Look for form fields or URL parameters named 'eping_host' in the plugin's PHP files.Affected if The eping_host parameter can be submitted via HTTP request to the plugin
A user is affected if e107 is installed with the ePing plugin present, and the functions.php file contains the eping_validaddr function that passes the eping_host parameter to shell execution functions without sanitizing shell metacharacters.
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 the eping_host parameter to reject or sanitize shell metacharacters before passing input to any system command execution functions.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1949 — 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-2005-1949 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