PHP

Path traversal vulnerability in Mikado-Themes Grill and Chow WordPress themes (versions through 1.6) that enables PHP Local File Inclusion (LFI) attacks. An unauthenticated remote attacker can exploit this vulnerability to read arbitrary files on the affected server, potentially exposing sensitive configuration files, database credentials, and other confidential data. The high CVSS score of 8.1 reflects significant impact on confidentiality and integrity, though exploitation requires higher attack complexity.

A Path Traversal vulnerability in Mikado-Themes GrandPrix WordPress theme (versions through 1.6) allows unauthenticated remote attackers to perform PHP Local File Inclusion (LFI) attacks, potentially leading to arbitrary file reading, information disclosure, and remote code execution. The vulnerability has a CVSS score of 8.1 (High) with high impact on confidentiality, integrity, and availability; exploitation requires medium attack complexity but no user interaction or privileges. KEV status and active exploitation data were not provided, but the high CVSS and LFI nature suggest significant real-world risk if POC is publicly available.

A Path Traversal vulnerability in Mikado-Themes MediClinic through version 2.1 enables unauthenticated remote attackers to conduct PHP Local File Inclusion (LFI) attacks, potentially allowing arbitrary file reading and code execution. The CVSS 8.1 score reflects high impact across confidentiality, integrity, and availability, though attack complexity is listed as HIGH. No public confirmation of active KEV exploitation or PoC availability is documented in standard feeds, but the high CVSS and LFI vector suggest this should be treated as a credible priority vulnerability.

PHP Local File Inclusion (LFI) vulnerability in Unfoldwp Magze versions up to 1.0.9 that allows unauthenticated remote attackers to include and execute arbitrary local files through improper control of filename parameters in PHP include/require statements. This is a network-accessible vulnerability with high attack complexity but complete impact on confidentiality, integrity, and availability (CVSS 8.1). The vulnerability likely affects WordPress plugin deployments where Magze is installed, and successful exploitation could lead to remote code execution through log poisoning or other LFI-to-RCE chains.

A security vulnerability in Unfoldwp Magways allows PHP Local File Inclusion (CVSS 8.1). High severity vulnerability requiring prompt remediation.

A security vulnerability in Unfoldwp Magty allows PHP Local File Inclusion (CVSS 8.1). High severity vulnerability requiring prompt remediation.

A security vulnerability in Unfoldwp Blogvy allows PHP Local File Inclusion (CVSS 8.1). High severity vulnerability requiring prompt remediation.

PHP Local File Inclusion (LFI) vulnerability in Unfoldwp Blogty plugin versions up to 1.0.11 that allows unauthenticated remote attackers to include and execute arbitrary local files through improper control of filename parameters in PHP include/require statements. The vulnerability has a CVSS score of 8.1 (High), indicating potential for confidentiality, integrity, and availability compromise. Active exploitation status and EPSS probability are critical factors in determining real-world risk severity.

PHP Local File Inclusion (LFI) vulnerability in Unfoldwp Blogprise WordPress plugin versions through 1.0.9, stemming from improper control of filename parameters in PHP include/require statements (CWE-98). An unauthenticated remote attacker can exploit this vulnerability over the network to read arbitrary files from the server filesystem, potentially leading to information disclosure, code execution, or further compromise. The CVSS 8.1 score reflects high severity with network accessibility and significant confidentiality/integrity/availability impact, though attack complexity is rated as high suggesting specific conditions must be met for exploitation.

PHP Local File Inclusion (LFI) vulnerability in Unfoldwp Blogmine versions up to 1.1.7 that allows unauthenticated remote attackers to include and execute arbitrary files on the server. The vulnerability stems from improper input validation on filename parameters used in PHP include/require statements (CWE-98). While the CVSS score of 8.1 reflects high impact potential across confidentiality, integrity, and availability, the AC:H (Attack Complexity: High) suggests exploitation requires specific conditions; KEV status, EPSS probability, and public POC availability are critical factors for determining actual prioritization.

PHP Local File Inclusion (LFI) vulnerability in Unfoldwp Blogbyte versions through 1.1.1, stemming from improper control of filenames in PHP include/require statements. An unauthenticated remote attacker can exploit this vulnerability with high complexity to achieve arbitrary code execution, information disclosure, or service disruption. While the CVSS score of 8.1 reflects severe potential impact, the High attack complexity (AC:H) suggests exploitation requires specific conditions or timing, and KEV/active exploitation status and POC availability remain unconfirmed from available intelligence.

PHP Local File Inclusion (LFI) vulnerability in g5theme Essential Real Estate plugin versions through 5.2.1, allowing unauthenticated remote attackers to include and execute arbitrary local files on the affected server. The vulnerability stems from improper control of filename parameters in PHP include/require statements (CWE-98), enabling potential information disclosure, code execution, and system compromise. While the CVSS score of 8.1 indicates high severity with high confidentiality and integrity impact, real-world exploitation depends on server configuration, file system permissions, and available local files for inclusion.

Local File Inclusion (LFI) vulnerability in WP Event Manager WordPress plugin versions through 3.1.49 that allows unauthenticated remote attackers to include and execute arbitrary PHP files from the server filesystem. This CWE-98 vulnerability has a CVSS score of 8.1 (High severity) with high impact on confidentiality, integrity, and availability. While the vulnerability requires specific conditions (AC:H), its network accessibility and lack of authentication requirements make it a significant risk for affected WordPress installations.

Cross-Site Scripting (XSS) vulnerability exists in askquery.php via the eid parameter in the CloudClassroom PHP Project. This allows remote attackers to inject arbitrary JavaScript in the context of a victim s browser session by sending a crafted URL, leading to session hijacking or defacement.

PHP Local File Inclusion (LFI) vulnerability in magentech Revo versions up to 4.0.26 that allows unauthenticated remote attackers to include and execute arbitrary local files through improper control of filename parameters in PHP include/require statements. An attacker can exploit this to read sensitive files, execute code, or compromise the affected system; the vulnerability requires user interaction (UI:R) but carries high impact across confidentiality, integrity, and availability. While no public exploit code or KEV status is currently confirmed in available intelligence, the combination of network accessibility, high CVSS score (7.5), and file inclusion primitives makes this a notable risk for unpatched Revo installations.

Path Traversal vulnerability enabling PHP Local File Inclusion (LFI) in Frenify Arlo through version 6.0.3. The vulnerability allows unauthenticated remote attackers to read arbitrary files from the server filesystem by manipulating path parameters, potentially exposing sensitive configuration files, source code, and credentials. With a CVSS score of 8.1 and network-accessible attack vector, this vulnerability poses significant risk to confidentiality and integrity; exploitation likelihood and active weaponization status cannot be confirmed from available data, but the straightforward nature of path traversal attacks suggests moderate-to-high real-world exploitation probability.

Path traversal vulnerability in WebGeniusLab Seofy Core (versions up to 1.4.5) that allows unauthenticated remote attackers to achieve PHP Local File Inclusion (LFI) with high complexity. The vulnerability enables attackers to read arbitrary files and potentially execute code on affected systems. No public indicators confirm active exploitation or KEV listing at this time, but the high CVSS score (8.1) and remote attack vector indicate significant risk requiring urgent patching.

PHP Local File Inclusion (LFI) vulnerability in Gavias Krowd versions up to 1.4.1 that allows unauthenticated remote attackers to include and execute arbitrary local files on the server. The vulnerability stems from improper control of filename parameters in PHP include/require statements (CWE-98), enabling attackers to read sensitive files or execute malicious code with high complexity but high impact including confidentiality, integrity, and availability compromise. No public exploit code or active exploitation reports are currently available in standard vulnerability databases, but the high CVSS score (8.1) and network-accessible attack vector indicate significant risk for unpatched installations.

PHP Local File Inclusion (LFI) vulnerability in SNS Anton theme versions up to 4.1 that allows unauthenticated remote attackers to include and execute arbitrary local files on the server. The vulnerability stems from improper input validation on filename parameters in PHP include/require statements (CWE-98), enabling attackers to read sensitive files or achieve remote code execution through log poisoning or other local file abuse techniques. With a CVSS score of 8.1 and network-based attack vector, this represents a critical risk to affected WordPress installations, particularly if actively exploited in the wild or if public proof-of-concept code is available.

A remote code execution vulnerability in snstheme Valen - Sport (CVSS 8.1). High severity vulnerability requiring prompt remediation.

PHP Local File Inclusion (LFI) vulnerability in the snstheme Avaz plugin that allows unauthenticated remote attackers to include arbitrary PHP files via improper control of filename parameters in include/require statements. The vulnerability affects Avaz versions through 2.8 and has a CVSS score of 8.1 (high severity), enabling attackers to execute arbitrary code, read sensitive files, and compromise system integrity without requiring authentication or user interaction.

PHP Local File Inclusion (LFI) vulnerability in BZOTheme GiftXtore versions through 1.7.4 that allows unauthenticated remote attackers to include and execute arbitrary local files on the server. This is a high-severity vulnerability (CVSS 8.1) that can lead to complete system compromise including confidentiality, integrity, and availability breaches. The vulnerability stems from improper validation of filename parameters in PHP include/require statements, enabling attackers to access sensitive files or execute malicious code without authentication.

PHP Local File Inclusion (LFI) vulnerability in BZOTheme Petito versions up to 1.6.2 that allows unauthenticated remote attackers to include and execute arbitrary local files on the server. The vulnerability exploits improper control of filename parameters in PHP include/require statements (CWE-98), enabling attackers to read sensitive files, execute code, or compromise server integrity with a CVSS score of 8.1 (High). While no public exploit code or KEV/EPSS data are confirmed in standard databases, the high CVSS and network accessibility make this a significant priority for affected organizations.

PHP Local File Inclusion (LFI) vulnerability in AncoraThemes Inset theme affecting versions through 1.18.0, allowing unauthenticated remote attackers to include and execute arbitrary local files on vulnerable servers. This CWE-98 vulnerability stems from improper control of filename parameters in PHP include/require statements, with a CVSS score of 8.1 (High) reflecting significant confidentiality, integrity, and availability impact. The moderate attack complexity (AC:H) suggests exploitation requires specific conditions or knowledge, though the network-accessible attack vector (AV:N) and lack of privilege requirements (PR:N) make this practically exploitable.

PHP Local File Inclusion (LFI) vulnerability in BZOTheme CraftXtore versions up to 1.7 that allows unauthenticated remote attackers to include and execute arbitrary local files through improper control of filename parameters in PHP include/require statements. The vulnerability has a CVSS score of 8.1 (high severity) with network accessibility and high impact to confidentiality, integrity, and availability. Exploitation requires moderate attack complexity but no user interaction or privileges, making it a significant risk if actively exploited or proof-of-concept code becomes public.

PHP Local File Inclusion (LFI) vulnerability in snstheme Nitan theme affecting versions through 2.9, allowing unauthenticated remote attackers to include and execute arbitrary local files on the server. While the CVSS score of 8.1 indicates high severity with potential for confidentiality, integrity, and availability impact, the attack complexity is marked as HIGH, suggesting exploitation requires specific conditions or server configurations. The vulnerability stems from improper validation of filename parameters in PHP include/require statements (CWE-98), a classic but dangerous class of web application flaws.

PHP Local File Inclusion (LFI) vulnerability in BZOTheme Fitrush versions up to 1.3.4 that allows unauthenticated remote attackers to include and execute arbitrary local files on the server. The vulnerability stems from improper control of filenames in PHP include/require statements (CWE-98), enabling attackers to read sensitive files or achieve remote code execution depending on server configuration. While the CVSS score is 8.1 (high severity), the CVSS vector indicates high attack complexity (AC:H), suggesting exploitation may require specific environmental conditions or knowledge of the target system's file structure.

A remote code execution vulnerability in snstheme BodyCenter - Gym (CVSS 8.1). High severity vulnerability requiring prompt remediation.

SQL injection in code-projects Chat System 1.0 allows remote authenticated attackers to manipulate the cid parameter in /user/confirm_password.php, potentially leading to data leakage or modification. A public exploit exists, but no active exploitation has been confirmed.

CVE-2025-5877 is a security vulnerability (CVSS 6.3). Risk factors: public PoC available.

A security vulnerability in eCharge Hardy Barth Salia PLCC (CVSS 6.3). Remediation should follow standard vulnerability management procedures.

The Broadstreet WordPress plugin before 1.51.8 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

The Newsletter WordPress plugin before 8.85 does not sanitise and escape some of its Form settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

The Newsletter WordPress plugin before 8.8.5 does not validate and escape some of its Widget options before outputting them back in a page/post where the block is embed, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

SQL injection vulnerability in PHPGurukul Maid Hiring Management System 1.0 affecting the /admin/search-booking-request.php file, where unsanitized user input in the 'searchdata' parameter allows unauthenticated remote attackers to execute arbitrary SQL queries. With a CVSS score of 7.3 and publicly disclosed exploit code available, this vulnerability poses significant risk to confidentiality, integrity, and availability of affected systems. Active exploitation is likely given the public POC availability and network-accessible attack vector.

We are asked to produce a JSON analysis of CVE-2025-5859. The input includes: description, CVSS vector (CVSS 4.0), EPSS, POC info, CPE, tags, etc. We need to synthesize all that into a comprehensive analysis, following the strict rules. Let's parse the data: - CVE-2025-5859: PHPGurukul Nipah Virus Testing Management System 1.0, SQL injection in /test-details.php via parameter "assignto". Remote, exploit disclosed. - CVSS 4.0 vector: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P (exploit maturity: P? Actually "E:P" maybe proof-of-concept, but likely "P" for public. Actually in the vector it's E:P). So base impact low on confidentiality, integrity, availability, no scope change. Attack complexity low, privileges low, user interaction none. So remote with low privileges, low impact. Overall base score might be computed, but we are to produce our own assessment for 3.1 and 4.0 vectors. - EPSS: 0.09%, percentile 25% - very low likelihood of exploitation in the wild. - POC: Publicly available (exploit disclosed). - KEV: not mentioned, so not in KEV. - Patch: No mention of patch availability. - CPE: exactly one: cpe:2.3:a:phpgurukul:nipah_virus_testing_management_system:1.0:*:*:*:*:*:*:* - References: GitHub issue with exploit (f1rstb100d/myCVE/issues/65), vendor site, vuldb entries. We need to produce a JSON with these fields: product_name, summary, technical_context, risk_assessment, affected_products, remediation, exploit_scenario, exploitation_conditions, attack_chain, confidence_notes, prevalence, prevalence_basis, assessed_cvss_vector, assessed_cvss_rationale, assessed_cvss40_vector. First, product_name: "1-3 words ONLY. The specific product or service name affected". It's "Nipah Virus Testing Management System". So product_name: "Nipah Virus Testing Management System" (3 words? Actually "Nipah Virus Testing Management System" is 4 words. But the rule says 1-3 words. I could shorten to "Nipah Virus Testing System" or just pick the primary product. The CPE says "nipah_virus_testing_management_system". The description calls it "PHPGurukul Nipah Virus Testing Management System". Since PHPGurukul is the vendor, product is "Nipah Virus Testing Management System". I'll try "Nipah Virus Testing System" to fit 3 words, but it's a specific name. I'll go with "Nipah Virus Testing Management System" but that's 4 words. Probably we can accept "Nipah Virus Testing Management System" as a single phrase? I'll output "Nipah Virus Testing Management System" because it's a proper name. Next, summary: "2-3 sentence plain-language summary for security professionals." Must not copy description, start with specific impact verb and product. For SQL injection, impact: "SQL injection in PHPGurukul Nipah Virus Testing Management System 1.0 allows remote attackers to manipulate the 'assignto' parameter in /test-details.php, leading to unauthorized database access." Include if actively exploited? No KEV, so not actively exploited. Mention POC exists, EPSS low. So: "SQL injection in PHPGurukul Nipah Virus Testing Management System 1.0 allows remote authenticated attackers to inject SQL via the 'assignto' parameter in /test-details.php. The vulnerability has a low CVSS 4.0 impact but publicly available exploit code and a low EPSS score (0.09%) suggest it is targeted rather than widespread." That's good. technical_context: Explain underlying technology, CWE. It's PHP web application with SQL injection. CWE-74 is generic "Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')", but actually SQL injection is usually CWE-89. The given CWE-74 is broader. I'll mention that parameter is directly used in SQL query without sanitization. Affected product: from CPE, PHPGurukul Nipah Virus Testing Management System 1.0. Provide technical context: "The vulnerability stems from improper handling of user-supplied input in the 'assignto' parameter of the /test-details.php endpoint, leading to SQL injection (CWE-89, categorized here as CWE-74)." But careful: stated CWE is 74, so I can say "CWE-74 injection, specifically SQL injection." risk_assessment: Assess real-world risk using CVSS, EPSS, POC, etc. CVSS 4.0 base score low? Compute: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N => base score for CVSS 4.0 might be 5.3 (Low) or something. But we can cite: CVSS 4.0 vector indicates low impact on confidentiality, integrity, availability, requiring low privileges. EPSS 0.09% (25th percentile) suggests low probability of widespread exploitation. POC publicly available but no active exploitation per KEV. So overall risk: low-to-medium for exposed systems. A real priority? Likely not critical unless the system processes sensitive health data. Use contrast: "CVSS 4.0 vector indicates low overall impact, and EPSS percentile is low, but the availability of public exploit code increases the risk for exposed internet-facing instances." Must state if any conflict: "CVSS 4.0 base score is low despite network attack vector, because the impact is assessed as low. However, if the database contains sensitive patient data, confidentiality impact may be higher in real-world context." affected_products: "PHPGurukul Nipah Virus Testing Management System version 1.0 (cpe:2.3:a:phpgurukul:nipah_virus_testing_management_system:1.0). No newer version available; vendor site is phpgurukul.com. Refer to advisory at https://vuldb.com/?id.311605." No patch link, so just mention the advisory references. remediation: Since no patch mentioned, we need to suggest specific compensating controls. "No vendor-released patch identified at time of analysis. As a workaround, implement input validation for the 'assignto' parameter, use parameterized queries or prepared statements, and apply web application firewall rules to block SQL injection attempts. Disable the /test-details.php endpoint if not needed. These mitigations may disrupt normal functionality and should be tested." Use the advisory URLs from references. Might mention the vendor site but no patch. So "Upgrade to a patched version when available from the vendor. In the interim, apply the workarounds described in the VulDB advisory." exploit_scenario: "A remote attacker with low-level authenticated access to the application sends a crafted HTTP request to /test-details.php with a malicious 'assignto' parameter, injecting SQL commands that extract, modify, or delete database contents. Public exploit code is available." exploitation_conditions: According to description: "The manipulation of the argument assignto leads to sql injection. The attack can be launched remotely." But the CVSS 4.0 vector says PR:L (low privileges required). So exploitation requires authentication. So: "Exploitation requires authentication to the application (CVSS PR:L). The attacker must have at least low-privilege access to the system. The vulnerability is in the /test-details.php endpoint, which processes the 'assignto' parameter. No other special conditions are required; the injection is achievable via a crafted HTTP request." So condition: authenticated user access. attack_chain: "Authenticate to application → Send crafted HTTP request to /test-details.php with SQL payload in 'assignto' parameter → Execute arbitrary SQL queries → Access, modify, or delete database records." That's 4 steps. confidence_notes: "Vulnerability confirmed by VulDB and public exploit (GitHub). EPSS score is low, but POC code exists. No vendor patch or advisory released; only VulDB provides details. No CISA KEV listing, so no confirmed active exploitation." Also note that CVSS 4.0 vector suggests low impact, but may be underrated. State: "Exact CVSS scoring is from VulDB; we independently confirm it aligns with description." prevalence: How widely deployed is this system? It's a niche application: "Nipah Virus Testing Management System" likely used in specific healthcare contexts, possibly only in certain regions. Not widely deployed like WordPress or Exchange. So prevalence: low. prevalence_basis: "niche healthcare application with limited deployment" (max 12 words). I'll say "niche viral testing management system, limited enterprise footprint." assessed_cvss_vector: We need our own CVSS 3.1 vector. The CVSS 4.0 input is: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. For 3.1, the mapping: Attack Vector: Network (AV:N), Attack Complexity: Low (AC:L), Privileges Required: Low (PR:L), User Interaction: None (UI:N), Scope: Unchanged (S:U) because subsequent system not impacted, Confidentiality: Low (C:L), Integrity: Low (I:L), Availability: Low (A:L). So vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L. That's a base score of 6.3 (Medium). So I'll output that. assessed_cvss_rationale: "Reflects network-exploitable SQL injection requiring low privileges with limited impact." That's one sentence. assessed_cvss40_vector: They provided a CVSS 4.0 vector. But we are to provide our own consistent with our 3.1 assessment. I'll just reuse the provided vector as my assessment because it's consistent: AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. However, the input vector includes E:P and environmental metrics, but for base vector we just need base metrics. Our own assessment should not include temporal/environmental. So simplified base: 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. That matches. I'll output that. Now, assemble JSON. Ensure no markdown, just braces. All fields as strings. Let's double-check every field: product_name: "Nipah Virus Testing Management System" summary: I'll craft: "SQL injection in PHPGurukul Nipah Virus Testing Management System 1.0 allows remote authenticated attackers to inject SQL via the 'assignto' parameter of /test-details.php. The vulnerability has publicly available exploit code but an EPSS score of 0.09%, indicating low probability of widespread exploitation. No active exploitation is currently confirmed by CISA KEV." technical_context: "The vulnerability occurs in the PHP-based web application when the 'assignto' parameter is used directly in SQL queries without proper sanitization. This is classified as CWE-74 (Injection) and more specifically SQL injection. Affected product is phpGurukul Nipah Virus Testing Management System version 1.0 as per CPE." risk_assessment: "CVSS 4.0 vector indicates a low-impact vulnerability (confidentiality, integrity, and availability impact rated low) despite network attack vector, requiring low authentication. EPSS score of 0.09% (25th percentile) and no CISA KEV listing suggest low real-world exploitation risk, though public exploit availability increases the risk for exposed instances. The low CVSS base score (approximately 5.3) reflects limited impact, but organizations handling sensitive health data may prioritize remediation to protect patient information." affected_products: "PHPGurukul Nipah Virus Testing Management System version 1.0 (cpe:2.3:a:phpgurukul:nipah_virus_testing_management_system:1.0). Vendor site: https://phpgurukul.com/. Advisory and details at VulDB ID 311605 and NVD entry." remediation: "No vendor-released patch has been identified. As a workaround, implement parameterized queries or prepared statements for the 'assignto' parameter, apply input validation, and consider restricting access to /test-details.php

SQL injection in PHPGurukul Nipah Virus Testing Management System 1.0 allows authenticated remote attackers to extract database contents via the searchdata parameter in /patient-report.php. A public exploit exists, but no active exploitation has been confirmed (EPSS 0.06%).

SQL injection in code-projects Patient Record Management System 1.0 allows remote authenticated attackers to execute arbitrary SQL commands via the itr_no parameter in /urinalysis_record.php. A public exploit exists, but no active exploitation has been reported and EPSS risk is low.

Critical SQL injection vulnerability in PHPGurukul BP Monitoring Management System version 1.0, specifically in the /registration.php file's emailid parameter. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has been publicly disclosed with exploit details available, creating immediate risk for unpatched installations.

Critical unrestricted file upload vulnerability in SourceCodester Client Database Management System 1.0, affecting the /user_update_customer_order.php endpoint. An unauthenticated remote attacker can upload arbitrary files by manipulating the 'uploaded_file' parameter, potentially leading to remote code execution, data integrity compromise, and service disruption. The vulnerability has a CVSS 7.3 score and poses moderate-to-high real-world risk given the unauthenticated attack vector and low complexity.

SQL injection vulnerability in PHPGurukul Employee Record Management System 1.3 allows remote authenticated attackers to manipulate the AdminName parameter in /admin/adminprofile.php, potentially exposing or modifying database contents. A public proof-of-concept exploit exists, though EPSS scores indicate a low probability of widespread exploitation (0.06%).

SQL injection in PHPGurukul Employee Record Management System 1.3 allows authenticated attackers to execute arbitrary SQL commands via the delid parameter in /admin/allemployees.php. A public exploit exists, but no active exploitation has been reported. The EPSS score is low (0.06%), indicating limited exploitation likelihood.

The WpEvently plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple parameters in all versions up to, and including, 4.4.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The Social Sharing Plugin - Sassy Social Share plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the heateor_mastodon_share parameter in all versions up to, and including, 3.3.75 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action, such as clicking on a link.

A cross-site scripting vulnerability in all (CVSS 7.2). High severity vulnerability requiring prompt remediation.

A security vulnerability in all (CVSS 5.3). Remediation should follow standard vulnerability management procedures.

Cross-site scripting (XSS) in code-projects Laundry System 1.0 allows remote authenticated attackers to inject arbitrary web scripts via the 'Type' parameter in /data/insert_type.php. A public exploit exists, but no active exploitation has been reported and EPSS risk is low.

Cross-site scripting (XSS) in code-projects Laundry System 1.0 allows remote authenticated users to inject arbitrary web scripts via the 'Type' parameter in /data/edit_type.php. A public exploit exists, but no active exploitation has been reported; EPSS score is low (0.05%).

SQL injection in PHPGurukul Employee Record Management System 1.3 allows authenticated remote attackers to manipulate database queries via the 'emp3ctc' parameter in /myexp.php. A public exploit exists, but no active exploitation has been reported and EPSS risk is low (0.06%).

SQL injection in PHPGurukul Employee Record Management System 1.3 allows remote authenticated attackers to manipulate the 'emp3workduration' parameter in /editmyexp.php, potentially leading to data exfiltration or modification. A public exploit is available, but no active exploitation has been reported (not in CISA KEV). EPSS score is low (0.06%), indicating limited exploitation likelihood.

SQL injection in PHPGurukul Employee Record Management System 1.3 allows authenticated attackers to manipulate the newpassword parameter in /resetpassword.php, potentially leading to unauthorized data access or modification. A public exploit exists, but no active exploitation has been confirmed.

SQL injection in code-projects Patient Record Management System 1.0 allows remote authenticated attackers to extract or manipulate database contents via the itr_no parameter in /view_dental.php. Public exploit code is available, but no active exploitation has been reported (not in CISA KEV). EPSS score is low (0.04%), indicating limited exploitation likelihood.

SQL injection in code-projects Patient Record Management System 1.0 allows remote authenticated attackers to extract or modify database contents via the itr_no or comp_id parameters in /birthing.php. A public exploit exists, but no active exploitation has been reported; EPSS score is low (0.04%).

Cross-site scripting (XSS) in code-projects Laundry System 1.0 allows an authenticated attacker to inject arbitrary JavaScript via the Customer parameter in /data/edit_laundry.php. A public exploit exists, but no active exploitation has been reported; EPSS score is low (0.05%).

Cross-site scripting (XSS) in code-projects Laundry System 1.0 allows an authenticated attacker to inject arbitrary JavaScript via the Customer parameter in /data/insert_laundry.php. A public exploit exists, but no active exploitation has been reported; EPSS score is low (0.05%).

PHP Local File Inclusion (LFI) vulnerability in ovatheme BRW versions up to 1.8.6, stemming from improper control of filename parameters in include/require statements. An authenticated attacker with low privileges can exploit this to read arbitrary files from the server filesystem, potentially gaining access to sensitive configuration files, source code, or credentials. The vulnerability requires network access and authenticated user status (CWE-98 improper input validation on file paths), with a CVSS score of 7.5 indicating high confidentiality and integrity impact.

PHP Local File Inclusion (LFI) vulnerability in WP Travel Engine affecting versions through 6.5.1. An authenticated attacker with low privileges can exploit improper filename control in PHP include/require statements to read arbitrary files from the server, potentially obtaining sensitive configuration data, credentials, or source code. While the CVSS score is moderate (7.5), the vulnerability requires authentication and higher attack complexity, but successful exploitation could lead to complete information disclosure and potential privilege escalation.

PHP Local File Inclusion (LFI) vulnerability in Magazine3's WP Multilang plugin versions up to 2.4.19, stemming from improper control of filenames in PHP include/require statements. An authenticated attacker with low privileges can exploit this vulnerability to read arbitrary local files on the affected WordPress server, potentially leading to information disclosure, code execution, or system compromise. The CVSS score of 7.5 reflects high confidentiality and integrity impact, though exploitation requires valid credentials and non-standard conditions (AC:H).

PHP Local File Inclusion (LFI) vulnerability in the WP Shopify plugin (versions up to 1.5.3) that allows authenticated attackers to include and execute arbitrary local files on the web server through improper control of filename parameters in PHP include/require statements. The vulnerability requires low-privilege user access (PR:L) and has moderate attack complexity (AC:H), but results in complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H), making it a significant risk for WordPress sites using this plugin.

PHP Local File Inclusion (LFI) vulnerability in choicehomemortgage AI Mortgage Calculator versions up to 1.0.1, caused by improper input validation on file inclusion statements. An authenticated attacker with low privileges can exploit this vulnerability over the network to read arbitrary files from the server, potentially leading to information disclosure, privilege escalation, or remote code execution. The high CVSS score of 7.5 reflects the severity of potential impacts (confidentiality, integrity, availability compromise), though the requirement for authenticated access and high attack complexity somewhat limit real-world exploitability.

SQL injection in code-projects Patient Record Management System 1.0 allows remote authenticated attackers to extract or modify database contents via the itr_no parameter in view_hematology.php. A public exploit exists, but no active exploitation has been confirmed (not in CISA KEV). EPSS score is low (0.04%), suggesting limited real-world risk.

SQL injection in PHPGurukul BP Monitoring Management System 1.0 allows remote authenticated attackers to execute arbitrary SQL commands via the 'memberage' parameter in /edit-family-member.php. A public exploit exists, but no active exploitation has been confirmed. EPSS score is low (0.06%), indicating limited exploitation likelihood.

The Simple History plugin for WordPress is vulnerable to sensitive data exposure via Detective Mode due to improper sanitization within the append_debug_info_to_context() function in versions prior to 5.8.1. When Detective Mode is enabled, the plugin’s logger captures the entire contents of $_POST (and sometimes raw request bodies or $_GET) without redacting any password‐related keys. As a result, whenever a user submits a login form, whether via native wp_login or a third‐party login widget, their actual password is written in clear text into the logs. An authenticated attacker or any user whose actions generate a login event will have their password recorded; an administrator (or anyone with database read access) can then read those logs and retrieve every captured password.

The Domain For Sale plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘class_name’ parameter in all versions up to, and including, 3.0.10 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

PHP Local File Inclusion (LFI) vulnerability in StylemixThemes Motors - Events plugin affecting versions up to 1.4.7, allowing unauthenticated remote attackers to include and execute arbitrary PHP files under certain conditions. With a CVSS score of 9.0 and network accessibility, this vulnerability enables complete system compromise through code execution. Active exploitation status and proof-of-concept availability should be verified through KEV database and security research databases.

Critical SQL injection vulnerability in PHPGurukul Local Services Search Engine Management System version 2.1, specifically in the /admin/edit-person-detail.php file where the 'editid' parameter is not properly sanitized. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion. The vulnerability has public exploit code available and may be actively exploited in the wild.

Critical SQL injection vulnerability in SourceCodester Open Source Clinic Management System v1.0, specifically in the /doctor.php file where the 'doctorname' parameter is insufficiently sanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially leading to unauthorized data access, modification, or deletion of sensitive healthcare information. The vulnerability has public exploit disclosure and may be actively exploited.

Stored cross-site scripting in code-projects Traffic Offense Reporting System 1.0 allows an authenticated attacker to inject arbitrary JavaScript via multiple parameters in /save-reported.php. Public exploit code exists, but EPSS score is low (0.05%) and no active exploitation has been reported.

Critical SQL injection vulnerability in code-projects Real Estate Property Management System version 1.0, specifically in the /Admin/EditCity.php endpoint. An unauthenticated remote attacker can exploit this vulnerability to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or deletion. The exploit has been publicly disclosed with proof-of-concept code available, and the vulnerability is likely being actively exploited in the wild.

SourceCodester Open Source Clinic Management System version 1.0 contains a critical SQL injection vulnerability in the /email_config.php file affecting the 'email' parameter. An unauthenticated remote attacker can exploit this to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or system compromise. Public disclosure and exploit code availability significantly elevate real-world risk.

SQL injection in Health Center Patient Record Management System 1.0 allows authenticated attackers to manipulate database queries via the itr_no parameter in /birthing_record.php. Public exploit code exists, but no active exploitation has been confirmed. EPSS score is low (0.04%), indicating limited exploitation likelihood.

Unrestricted file upload in SourceCodester Open Source Clinic Management System 1.0 allows remote authenticated attackers to upload arbitrary files via the website_image parameter in /manage_website.php. Public exploit code exists, but no active exploitation has been confirmed. EPSS score is low (0.10%), indicating limited exploitation likelihood.

The StageShow plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘anchor’ parameter in all versions up to, and including, 10.0.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The Developer Formatter plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Custom CSS in all versions up to, and including, 2015.0.2.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.

The Paged Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'gallery' shortcode in all versions up to, and including, 0.7 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The WordPress Ajax Load More and Infinite Scroll plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id’ parameter in all versions up to, and including, 1.6.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The Hide It plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'hideit' shortcode in all versions up to, and including, 1.0.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The WP-Addpub plugin for WordPress is vulnerable to SQL Injection via the 'wp-addpub' shortcode in all versions up to, and including, 1.2.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The Runners Log plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'runnerslog' shortcode in all versions up to, and including, 3.9.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The BNS Featured Category plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'bnsfc' shortcode in all versions up to, and including, 2.8.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The Freemind Viewer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'freemind' shortcode in all versions up to, and including, 1.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The ESV Bible Shortcode for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'esv' shortcode in all versions up to, and including, 1.0.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The Knowledge Base plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'kbalert' shortcode in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The WP Email Debug WordPress plugin (versions 1.0-1.1.0) contains a critical privilege escalation vulnerability (CVE-2025-5486) stemming from missing capability checks in the WPMDBUG_handle_settings() function. Unauthenticated attackers can exploit this to modify plugin settings, redirect administrator emails to attacker-controlled addresses, and trigger password resets to gain full administrative access to affected WordPress installations. The CVSS 9.8 score reflects network-based exploitation with zero complexity and no authentication required, representing a critical severity threat with high real-world exploitation potential.

The WP Online Users Stats plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.0. This is due to missing nonce validation within the hk_dataset_results() function. This makes it possible for unauthenticated attackers to inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The WP Online Users Stats plugin for WordPress is vulnerable to time-based SQL Injection via the ‘table_name’ parameter in all versions up to, and including, 1.0.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Editor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Cross-Site Request Forgery in the Anti-Spam: Spam Protection plugin for WordPress allows unauthenticated attackers to delete pending comments and re-enable blocked users by tricking a site administrator into clicking a malicious link. The vulnerability affects all versions up to and including 2024.7 due to missing nonce validation in specific files. No public exploit or active exploitation has been identified, and the EPSS score is low at 0.03%.

A security vulnerability in all (CVSS 4.3). Remediation should follow standard vulnerability management procedures.

A security vulnerability in all (CVSS 6.4). Remediation should follow standard vulnerability management procedures.

The Short URL WordPress plugin through version 1.6.8 contains a SQL injection vulnerability (CWE-89) in an unsanitized parameter used directly in SQL statements. This vulnerability is exploitable by low-privileged users (subscribers), allowing attackers to extract sensitive database information, modify data, or potentially execute arbitrary code. With a CVSS score of 8.8 and network-accessible attack vector requiring only low privilege level, this represents a critical risk to WordPress installations using vulnerable plugin versions.