CVE-2025-63562VulnerabilityPublished 31 Oct 2025

CVE-2025-63562: Summer-Pearl-Group-Broken-Access-Control · n/a

Affects Summer-Pearl-Group-Broken-Access-ControlSource CVE Database V5

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.0.2 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.2

CVSS:3.1/AC:L/AV:N/A:L/C:L/I:L/PR:L/S:U/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: Low
Confidentiality: Low
Integrity: Low
Privileges Required: Low
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade stolichnayer/Summer-Pearl-Group-Broken-Access-Control to 1.0.2.

Affected software

Product	Affected	Fixed in
GitHubstolichnayer/Summer-Pearl-Group-Broken-Access-Control`pkg:github/stolichnayer/Summer-Pearl-Group-Broken-Access-Control`Other threats	Affected <1.0.2	Fixed in 1.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify their platform version and upgrade to Summer Pearl Group Vacation Rental Management Platform version 1.0.2 or later, where the vulnerability is addressed. In the absence of an official patch, organizations should implement strict server-side authorization checks to validate user permissions on all resource-related operations, ensuring that users can only act on resources they own or are authorized to manage. Conduct thorough access control audits and implement role-based access control (RBAC) policies to minimize privilege exposure. Monitor logs for unusual activity related to resource manipulation, especially from authenticated users with limited privileges. Employ multi-factor authentication (MFA) to reduce the risk of credential compromise. Regularly review and update security policies and train staff on secure credential handling. If possible, isolate the platform within segmented network zones to limit lateral movement in case of compromise. Engage with the vendor for timely security updates and advisories.

Description

Summer Pearl Group Vacation Rental Management Platform prior to v1.0.2 suffers from insufficient server-side authorization. Authenticated attackers can call several endpoints and perform create/update/delete actions on resources owned by arbitrary users by manipulating request parameters (e.g., owner or resource id).

Impact

For European organizations using the Summer Pearl Group Vacation Rental Management Platform, this vulnerability could lead to unauthorized access and modification of sensitive customer and business data. Attackers with valid credentials could manipulate bookings, customer information, or financial records, potentially causing data breaches, financial loss, and reputational damage. Given the platform’s role in managing vacation rentals, unauthorized changes could disrupt operations, leading to customer dissatisfaction and legal liabilities under GDPR due to improper handling of personal data. The impact on confidentiality and integrity is significant, as attackers can access and alter data without detection. Although availability is not directly affected, the operational disruption caused by unauthorized data changes could indirectly impact service continuity. The requirement for authentication limits exploitation to insiders or compromised accounts, but this still represents a critical risk in environments where credential theft or insider threats are possible. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks.

CWE-284Improper Access Control (opens in a new tab)
Pillar weaknessCWE Top 25 (2025): #19OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Embedding Scripts within Scripts (opens in a new tab)
Modification of Windows Service Configuration (opens in a new tab)
Malicious Root Certificate (opens in a new tab)
Intent Spoof (opens in a new tab)
WebView Exposure (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/Stolichnayer/Summer-Pearl-Group-Broken-Access-Control (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Oct 2025, 20:13 UTC

WeaknessesCWE-284

Technical details

References

Community reviews

Related threats