CVE-2026-4907VulnerabilityPublished 27 Mar 2026

CVE-2026-4907: Page Replica · Server-Side Request Forgery

Affects Page ReplicaSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system 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 Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system 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 Vulnerable System 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 Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2026
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

Affected software

Product	Affected	Fixed in
Page-ReplicaPage Replica	Affected =e4a7f52e75093ee318b4d5a9a9db6751050d2ad0	Fixed in–

AI-suggested

To mitigate CVE-2026-4907, organizations should first implement strict input validation and sanitization on the 'url' parameter in the sitemap.fetch function to prevent arbitrary URL requests. Network-level controls should be enforced to restrict outbound HTTP requests from the Page-Replica server to only trusted destinations, using firewall rules or proxy whitelisting. Employing web application firewalls (WAFs) with custom rules to detect and block suspicious SSRF patterns can provide additional protection. Monitoring and logging all outgoing requests from the server can help detect exploitation attempts early. Given the absence of vendor patches, organizations should consider isolating the Page-Replica service in a segmented network zone with minimal access to sensitive internal resources. Regularly review and update the software to the latest rolling release versions, as future updates may address the vulnerability. If feasible, temporarily disabling or restricting the sitemap.fetch functionality until a patch is available can reduce risk. Finally, maintain awareness of threat intelligence sources for any emerging exploit activity or vendor updates.

Description

A vulnerability was identified in Page-Replica Page Replica up to e4a7f52e75093ee318b4d5a9a9db6751050d2ad0. The impacted element is the function sitemap.fetch of the file /sitemap of the component Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit is publicly available and might be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The SSRF vulnerability in Page-Replica can have significant impacts on organizations running this software. Attackers can leverage the vulnerability to make the server perform unauthorized requests, potentially accessing internal-only services, sensitive metadata, or administrative interfaces not exposed externally. This can lead to information disclosure, such as leaking internal IP addresses, cloud metadata, or confidential data. Additionally, attackers may pivot from SSRF to further compromise internal systems, escalate privileges, or disrupt services. The lack of authentication and user interaction requirements lowers the barrier to exploitation, increasing risk. The rolling release nature of the product complicates patching, potentially leaving many deployments vulnerable for extended periods. Organizations relying on Page-Replica for web infrastructure or content delivery may face data breaches, service interruptions, or reputational damage if exploited. While no active exploitation is reported, the public exploit availability and vendor silence heighten urgency for mitigation.

Summary

CVE-2026-4907 is a server-side request forgery (SSRF) vulnerability found in the Page-Replica software, affecting the sitemap.fetch function within the /sitemap endpoint of the Endpoint component. The vulnerability arises from improper validation of the 'url' parameter, which an attacker can manipulate to cause the server to send arbitrary HTTP requests to internal or external systems. This can lead to unauthorized access to internal services, bypassing network restrictions, and potentially exposing sensitive data or enabling further attacks such as internal port scanning or exploitation of other internal vulnerabilities. The vulnerability is remotely exploitable without requiring authentication or user interaction, increasing its risk profile. The product follows a rolling release model, which means affected versions are not clearly delineated, complicating patch management. Despite early vendor notification, no response or patch has been issued, and a public exploit is available, increasing the likelihood of exploitation. The CVSS 4.0 base score is 5.3 (medium severity), reflecting the moderate impact on confidentiality, integrity, and availability, and the ease of exploitation. The vulnerability does not require privileges or user interaction but has limited scope and impact compared to higher severity SSRF flaws. No known exploits in the wild have been reported yet, but the availability of a public exploit raises concern for imminent attacks.

References

Community reviews

Loading reviews…