CVE-2026-10287
Deferred Deferred - Pending Action
Server-Side Request Forgery in SEO Meta Tag Extractor

Publication date: 2026-06-01

Last updated on: 2026-06-01

Assigner: VulDB

Description
A vulnerability was determined in SourceCodester SEO Meta Tag Extractor 1.0. This vulnerability affects the function get_headers of the file /index.php. This manipulation of the argument url causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-01
Last Modified
2026-06-01
Generated
2026-06-22
AI Q&A
2026-06-02
EPSS Evaluated
2026-06-20
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sourcecodester seo_meta_tag_extractor 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

This SSRF vulnerability allows unauthorized attackers to access internal services and potentially retrieve sensitive data, which could lead to unauthorized disclosure of personal or protected information.

Such unauthorized access and data exposure may result in non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive and personal data against unauthorized access.

Therefore, exploitation of this vulnerability could compromise confidentiality and integrity of data, impacting compliance with these common standards and regulations.

Detection Guidance

This vulnerability can be detected by monitoring for unusual POST requests to the vulnerable application, specifically those containing the url parameter that triggers server-side requests.

You can test the vulnerability by sending crafted POST requests with the url parameter pointing to internal or private IP addresses and observing if the server fetches and returns internal content.

Example commands to test this include using curl to send POST requests with a crafted url parameter:

  • curl -X POST -d "url=http://127.0.0.1" http://target/index.php
  • curl -X POST -d "url=http://169.254.169.254/latest/meta-data/" http://target/index.php

If the server responds with internal data or metadata, it indicates the presence of the SSRF vulnerability.

Mitigation Strategies

Immediate mitigation steps include implementing strict validation and filtering of the url parameter to prevent SSRF attacks.

  • Allow only http and https schemes in the url parameter.
  • Resolve hostnames to IP addresses and reject requests targeting private, loopback, or link-local IP ranges.
  • Disable following HTTP redirects in server-side requests to prevent bypassing IP restrictions.
  • Set request timeouts and limit content length to reduce the impact of malicious requests.

Additionally, monitor and restrict access to internal services and metadata endpoints to reduce exposure.

Executive Summary

This vulnerability exists in SourceCodester SEO Meta Tag Extractor 1.0, specifically in the get_headers function of the /index.php file.

The issue arises from manipulation of the 'url' argument, which allows an attacker to perform server-side request forgery (SSRF).

This means an attacker can make the server send requests to unintended locations, potentially accessing internal systems or resources.

The attack can be initiated remotely and the exploit has been publicly disclosed.

Impact Analysis

The vulnerability can lead to unauthorized access to internal or protected resources by tricking the server into making requests on behalf of the attacker.

It can result in confidentiality, integrity, and availability impacts, as indicated by the CVSS scores showing low confidentiality, integrity, and availability impacts.

An attacker could potentially access sensitive information, manipulate data, or disrupt services by exploiting this SSRF vulnerability.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-10287. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart