Security readout for executives and security teams
Plain-English summary
Pegasus CMS 1.0 has a critical flaw that can let an unauthenticated remote attacker run commands on the web server. A successful compromise could expose data, modify site content, or disrupt service. Public exploit material is referenced, but the provided sources do not show confirmed active exploitation.
Executive priority
Prioritize this as urgent if Pegasus CMS 1.0 is in use, especially on public websites. The business risk is server compromise, data exposure, and service disruption. If no instances exist, document non-exposure and continue monitoring vendor and CVE updates.
Technical view
The issue is reported in Pegasus CMS 1.0, involving unsafe eval behavior in the extra_fields.php plugin reachable through a CMS submission path. The CVSS 3.1 score is 9.8 because exploitation is network-accessible, low complexity, requires no privileges, and can fully affect confidentiality, integrity, and availability.
Likely exposure
Risk is highest for internet-facing Pegasus CMS 1.0 deployments, especially if the affected plugin and submission functionality are enabled. Internal deployments are still exposed to any attacker with network reachability. The source bundle does not identify other affected versions.
Exploitation context
ExploitDB and VulnCheck references indicate public exploit knowledge exists. The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Treat exposure as urgent because unauthenticated RCE against a CMS can lead to server takeover.
Researcher notes
Sources describe RCE via unsafe eval, while the bundle lists CWE-22, which may be inconsistent. No patch version or vendor remediation is named in the provided sources. Avoid assuming broader product impact beyond Pegasus CMS 1.0.
Mitigation direction
- Identify any Pegasus CMS 1.0 deployments and owners.
- Check Wisdom or trusted advisories for fixed versions or official guidance.
- Remove or disable unused Pegasus CMS 1.0 instances.
- Restrict network access to affected CMS instances where removal is not immediate.
- Increase monitoring for suspicious CMS submission activity.
Validation and detection
- Inventory web assets for Pegasus CMS 1.0.
- Confirm whether the affected extra_fields.php plugin is present.
- Determine whether CMS submission functionality is reachable externally.
- Review web logs for unusual unauthenticated POST activity.
- Verify remediation against vendor or advisory guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2019-25687 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- ExploitDB-46542CVE reference · exploit
- Official Product HomepageCVE reference · product
- VulnCheck Advisory: Pegasus CMS 1.0 Remote Code Execution via extra_fields.phpCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.