CVE-2019-25687
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 · uneditedPegasus CMS 1.0 contains a remote code execution vulnerability in the extra_fields.php plugin that allows unauthenticated attackers to execute arbitrary commands by exploiting unsafe eval functionality. Attackers can send POST requests to the submit.php endpoint with malicious PHP code in the action parameter to achieve code execution and obtain an interactive shell.
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 confidencePegasus CMS 1.0 contains an unauthenticated remote code execution vulnerability in the extra_fields.php plugin. The vulnerability stems from unsafe eval functionality that processes the action parameter from POST requests to the submit.php endpoint, allowing attackers to inject and execute arbitrary PHP code.
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= 1.0CVSS 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.
-
Confirm Pegasus CMS versionLocate the CMS installation directory and identify the installed version by checking version files, headers, or the CMS admin panel for the exact version number. Compare against the affected version 1.0.Affected if The installed version is Wisdom Pegasus Cms 1.0
-
Locate extra_fields.php plugin fileSearch the web root and plugin directories for a file named extra_fields.php. Common paths may include /plugins/, /includes/, or the root web directory.Affected if The file extra_fields.php exists in the installation
-
Verify submit.php endpoint accessibilityCheck for the presence of submit.php in the web root or plugin directories. This endpoint accepts POST requests with the action parameter.Affected if submit.php is accessible via HTTP/HTTPS without authentication
-
Inspect eval usage in extra_fields.phpOpen extra_fields.php and search for eval() function calls. Verify if user input (particularly the action parameter from POST requests) is passed directly to eval without sanitization.Affected if The code contains unsafe eval() that processes the action parameter without input validation
A user is affected if they are running Wisdom Pegasus Cms version 1.0 with the extra_fields.php plugin present and accessible, as this allows unauthenticated remote code execution through the submit.php endpoint.
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 dataImmediate mitigation requires disabling or restricting access to the vulnerable submit.php endpoint until a patch can be applied. The fix involves removing unsafe eval usage and implementing proper input validation/sanitization in the extra_fields.php plugin.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-25687 — 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-2019-25687 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