Security readout for executives and security teams
Plain-English summary
PbootCMS v0.9.8 is reported to have a cross-site request forgery issue in an administrative message modification path that can lead to PHP code injection. The strongest concern is compromise through an authenticated administrator's browser session. Public metadata does not provide a CVSS score, confirmed patch, or evidence of active exploitation.
Executive priority
Prioritize validation if PbootCMS is present in internet-facing or business-critical sites. The potential impact is serious because PHP code injection can affect site integrity, but evidence is incomplete and no active exploitation is cited.
Technical view
The CVE describes CSRF against `admin.php/Message/mod/id/19.html?backurl=/index.php`, with PHP code injection through the `recontent` parameter. The record identifies PbootCMS v0.9.8 specifically. Available metadata lacks CWE, CPE, CVSS, and vendor remediation detail, so exposure assessment depends on local version and admin-interface reachability.
Likely exposure
Organizations are likely exposed only if they run PbootCMS v0.9.8, especially where administrative sessions are reachable by users browsing untrusted content. The source bundle does not identify broader affected versions or package identifiers.
Exploitation context
The CVE includes a public GitHub proof-of-concept reference, but the bundle does not state active exploitation and KEV is false. Treat this as publicly documented exploitation technique, not confirmed in-the-wild exploitation.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, or vendor advisory is included. Analysis should stay tied to PbootCMS v0.9.8 and the referenced admin message path until additional vendor or maintainer evidence confirms scope and remediation.
Mitigation direction
- Confirm whether any PbootCMS v0.9.8 instances exist.
- Check PbootCMS vendor or project guidance for fixed versions.
- Restrict administrative interface access to trusted networks or VPN.
- Review CSRF protections around administrative form submissions.
- Reduce administrator exposure to untrusted links while remediation is pending.
Validation and detection
- Inventory CMS technologies and identify PbootCMS versions.
- Review web logs for access to the referenced admin message path.
- Confirm admin endpoints require authentication and CSRF validation.
- Check whether the `recontent` field accepts executable PHP content.
- Document compensating controls if no vendor fix is available.
Public sources used
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.
CVE-2018-10132 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/vQAQv/Request-CVE-ID-PoC/blob/master/PbootCMS/v0.9.8/CSRF.mdCVE reference · x_refsource_MISC
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.