CPE, qui signifie Common Platform Enumeration, est un système normalisé de dénomination du matériel, des logiciels et des systèmes d'exploitation. CPE fournit un schéma de dénomination structuré pour identifier et classer de manière unique les systèmes informatiques, les plates-formes et les progiciels sur la base de certains attributs tels que le fournisseur, le nom du produit, la version, la mise à jour, l'édition et la langue.
CWE, ou Common Weakness Enumeration, est une liste complète et une catégorisation des faiblesses et des vulnérabilités des logiciels. Elle sert de langage commun pour décrire les faiblesses de sécurité des logiciels au niveau de l'architecture, de la conception, du code ou de la mise en œuvre, qui peuvent entraîner des vulnérabilités.
CAPEC, qui signifie Common Attack Pattern Enumeration and Classification (énumération et classification des schémas d'attaque communs), est une ressource complète, accessible au public, qui documente les schémas d'attaque communs utilisés par les adversaires dans les cyberattaques. Cette base de connaissances vise à comprendre et à articuler les vulnérabilités communes et les méthodes utilisées par les attaquants pour les exploiter.
Services & Prix
Aides & Infos
Recherche de CVE id, CWE id, CAPEC id, vendeur ou mots clés dans les CVE
Multiple cross-site scripting (XSS) vulnerabilities in phpGedView before 2.65 allow remote attackers to inject arbitrary HTML or web script via (1) descendancy.php, (2) index.php, (3) individual.php, (4) login.php, (5) relationship.php, (6) source.php, (7) imageview.php, (8) calendar.php, (9) gedrecord.php, (10) login.php, and (11) gdbi_interface.php. NOTE: some aspects of vector 10 were later reported to affect 4.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Métriques
Métriques
Score
Gravité
CVSS Vecteur
Source
V2
4.3
AV:N/AC:M/Au:N/C:N/I:P/A:N
nvd@nist.gov
EPSS
EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.
Score EPSS
Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
21.87%
–
–
2022-04-03
–
–
21.87%
–
–
2022-07-17
–
–
21.87%
–
–
2022-07-24
–
–
21.87%
–
–
2022-11-13
–
–
21.87%
–
–
2022-11-20
–
–
21.87%
–
–
2022-12-04
–
–
21.87%
–
–
2023-01-01
–
–
21.87%
–
–
2023-02-19
–
–
21.87%
–
–
2023-03-12
–
–
–
1.82%
–
2023-07-02
–
–
–
1.82%
–
2024-02-11
–
–
–
1.82%
–
2024-06-02
–
–
–
1.82%
–
2024-06-30
–
–
–
1.62%
–
2024-12-22
–
–
–
2.28%
–
2025-02-16
–
–
–
2.28%
–
2025-01-19
–
–
–
2.28%
–
2025-02-16
–
–
–
2.28%
–
2025-03-18
–
–
–
–
0.89%
2025-03-30
–
–
–
–
1.94%
2025-03-30
–
–
–
–
1.94,%
Percentile EPSS
Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11907/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/calendar.php?action=today&day=1&month=jan&year="><iframe>
http://www.example.com/phpgedview/calendar.php?action=today&day=1&month=<iframe>
http://www.example.com/phpgedview/calendar.php?action=today&day=<iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11894/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/gdbi_interface.php?action=delete&pid=<iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11891/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/gedrecord.php?pid=<iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11890/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/imageview.php?filename=<iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11880/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/index.php?rootid="><iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11882/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/individual.php?pid="><iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11905/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/login.php?&changelanguage=yes&NEWLANGUAGE=<iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11903/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/login.php?url=/index.php?GEDCOM="><iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11904/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/login.php?action=login&username="><iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11910/info
It is reported that PhpGedView is susceptible to a remote SQL injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input prior to including it in an SQL query.
This issue allows remote attackers to manipulate query logic, leading to unauthorized access and the disclosure of potentially sensitive information. The issue also allows the possible corruption of database data leading to a loss of integrity. SQL injection attacks may also be used to exploit latent vulnerabilities in the underlying database.
This issue has been reported to effect PhpGedView 2.65beta5 and earlier.
http://www.example.com/phpgedview/placelist.php?level=1[Evil_Query]
http://www.example.com/phpgedview/placelist.php?level=1&parent[0]=[Evil_Query]
http://www.example.com/phpgedview/placelist.php?level=2&parent[0]=&parent[1]=[Evil_Query]
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11906/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/relationship.php?path_to_find="><iframe>
http://www.example.com/phpgedview/relationship.php?path_to_find=0&pid1="><iframe>
http://www.example.com/phpgedview/relationship.php?path_to_find=0&pid1=&pid2="><iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11888/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/source.php?sid=<iframe>
Date de publication : 2004-01-11 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11925/info
It is reported that PhpGedView is susceptible to a remote SQL injection vulnerability. This issue is due to a failure in the application to properly sanitize user-supplied input prior to including it in an SQL query.
This issue allows remote attackers to manipulate query logic. The issue could theoretically be exploited to compromise the software by performing unauthorized actions on the database, such as modifying or viewing data. SQL injection attacks may also be used to exploit latent vulnerabilities in the underlying database. This may depend on the nature of the query being manipulated as well as the capabilities of the database implementation.
This issue has been reported to effect PhpGedView 2.65beta5 and earlier.
http://www.example.com/phpgedview/timeline.php?pids=[Evil_Query]
Date de publication : 2004-01-18 23h00 +00:00 Auteur : JeiAr EDB Vérifié : Yes
source: https://www.securityfocus.com/bid/11868/info
It is reported that PhpGedView is affected by a cross-site scripting vulnerability. This issue is due to a failure of the application to properly sanitize user-supplied URI input.
This issue could permit a remote attacker to create a malicious URI link that includes hostile HTML and script code. If this link were to be followed, the hostile code may be rendered in the web browser of the victim user. This would occur in the security context of the affected web site and may allow for theft of cookie-based authentication credentials or other attacks.
http://www.example.com/phpgedview/descendancy.php?pid=<iframe>
Products Mentioned
Configuraton 0
Phpgedview>>Phpgedview >> Version To (including) 2.65