Security readout for executives and security teams
Plain-English summary
CVE-2025-45947 is reported as a critical remote code-execution flaw in PHPGurukul Online Banquet Booking System 1.2. An attacker may compromise the server through the account password-change component without credentials or user interaction, potentially exposing data, altering the application, or disrupting service.
Executive priority
Treat confirmed internet-facing version 1.2 deployments as immediate remediation and investigation priorities. The potential business impact includes complete application-server compromise. Systems without confirmed exposure should still receive urgent inventory validation because the supplied affected-product metadata is incomplete.
Technical view
The report identifies CWE-94 code injection in /obbs/change-password.php. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges or user interaction required, with high confidentiality, integrity, and availability impact. The supplied affected-product metadata is incomplete despite the description naming version 1.2.
Likely exposure
Highest risk applies to internet-accessible deployments of PHPGurukul Online Banquet Booking System 1.2 where /obbs/change-password.php is reachable. Exposure for other versions is not established by the supplied sources. The bundle provides no CPE identifiers or reliable vendor inventory mapping.
Exploitation context
The supplied sources describe a potentially unauthenticated, network-based attack path. The CVE is not listed as KEV in the bundle, and no cited evidence confirms active exploitation. Absence from KEV does not prove exploitation is not occurring.
Researcher notes
The record asserts arbitrary code execution but provides limited affected-version and remediation detail. Validate exposure conservatively and distinguish the CVE description from independently confirmed behavior. Do not infer additional affected versions, patch availability, or exploitation activity from the CVSS score alone.
Mitigation direction
- Identify and prioritize every deployment of Online Banquet Booking System 1.2.
- Check current vendor or project guidance for an official correction or supported upgrade.
- Restrict external access to the application until authoritative remediation is available.
- Isolate affected servers and strengthen monitoring if the application must remain operational.
- Preserve relevant logs before remediation when compromise is suspected.
Validation and detection
- Confirm the installed product and version using deployment records and application files.
- Determine whether /obbs/change-password.php is reachable from untrusted networks without authentication.
- Review web and system logs for unexpected requests, process activity, or application changes.
- Check affected hosts for unauthorized files, accounts, persistence, and configuration modifications.
- After remediation, verify the vulnerable endpoint is removed, corrected, or appropriately restricted.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-45947 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.
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:N/S:U/C:H/I:H/A:H3.95.9CISA-ADPVulnerability 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
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://github.com/VasilVK/CVE/blob/main/CVE-2025-45947/README.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 Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.