Security readout for executives and security teams
Plain-English summary
Fantastic Blog CMS 1.0 contains a cross-site scripting flaw in the address field handled by pageEditMember.php. An attacker could cause script execution in another user’s browser, potentially exposing session-accessible information or altering actions within that user’s permissions. User interaction is required, and the supplied sources do not report service disruption.
Executive priority
Treat this as a prompt remediation item for internet-facing or broadly accessible installations, especially where privileged administrators may view member data. It is not supported as an emergency active-exploitation event, but browser-session and content integrity risks justify timely inventory, exposure reduction, and remediation validation.
Technical view
CVE-2025-65337 is classified as CWE-79 with CVSS 3.1 score 6.1. The vector indicates network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality and integrity impact. The bundle identifies pageEditMember.php’s address field, but does not establish whether the flaw is stored or reflected.
Likely exposure
Exposure is most likely where Fantastic Blog CMS 1.0 is deployed and pageEditMember.php is web-accessible. The CVSS vector indicates authentication is not required for the vulnerable interaction, although successful impact requires another user’s interaction. The structured affected-product data and CPE mapping are incomplete.
Exploitation context
The supplied bundle does not show CISA KEV listing or confirmed active exploitation. A public GitHub research reference exists, but that alone does not establish real-world attacks. No exploit prevalence, affected deployment count, or confirmed attack campaign is documented in the provided evidence.
Researcher notes
The record identifies an address-field XSS sink in pageEditMember.php, but the supplied description omits data flow, persistence, authentication workflow, browser context, and fixed-version information. Structured affected fields are listed as unavailable despite the narrative naming Fantastic Blog CMS 1.0. Avoid assuming XSS subtype or patch status without further vendor evidence.
Mitigation direction
- Identify and restrict exposed Fantastic Blog CMS 1.0 installations until remediation is confirmed.
- Check the project or vendor guidance for an official patch or fixed release.
- Apply context-appropriate output encoding where the address value is rendered.
- Validate and sanitize address input as defense in depth, without relying on filtering alone.
- Use browser security controls such as a restrictive Content Security Policy to reduce impact.
Validation and detection
- Inventory deployments and confirm whether Fantastic Blog CMS 1.0 is present.
- Determine whether pageEditMember.php is reachable from untrusted networks or users.
- Review address-field rendering for context-appropriate output encoding.
- Use an authorized, non-destructive security test to confirm scripts cannot execute.
- Confirm security controls remain effective after application updates or configuration changes.
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.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCVE-2025-65337 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
- Medium
- CVSS
- 6.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
SSVC decision data
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:R/S:C/C:L/I:L/A:N2.82.7CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.1MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.sourcecodester.com/php/12258/fantastic-blog-cms-php.htmlCVE reference, mitre
- https://github.com/um-dsp/TaintRadar/blob/main/XSS_cve/fantasticblog/XSS1.mdCVE reference, mitre
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 Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.