PHP

SQL injection in Jasmin Ransomware 1.0.0 and 1.0.1 allows remote authenticated attackers to extract sensitive data from the database via the Search parameter in /dashboard.php. A public exploit exists, but EPSS score is low (0.07%) and no active exploitation has been reported.

A SQL injection vulnerability (CVSS 7.3). Risk factors: EPSS 28% exploitation probability, public PoC available.

SQL injection in FoxCMS up to 1.2.5 allows authenticated remote attackers to execute arbitrary SQL commands via the 'ids' parameter in the batchCope function of Download.php. A public exploit is available, but no active exploitation has been reported (not in CISA KEV). EPSS score is low (0.07%), suggesting limited exploitation risk.

The Slider, Gallery, and Carousel by MetaSlider plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘aria-label’ parameter in all versions up to, and including, 3.98.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 YITH WooCommerce Wishlist plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id’ parameter in all versions up to, and including, 4.5.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 Appointment Booking Calendar - Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's ssa_admin_upcoming_appointments, ssa_admin_upcoming_appointments, and ssa_past_appointments shortcodes in all versions up to, and including, 1.6.8.30 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 Restrict File Access plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 1.1.2 via the output() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.

The Image Resizer On The Fly WordPress plugin (versions ≤1.1) contains a critical arbitrary file deletion vulnerability in its 'delete' task that allows unauthenticated attackers to remove arbitrary files from the server without authentication. This vulnerability can facilitate remote code execution by deleting critical files such as wp-config.php, leading to complete WordPress installation compromise. With a CVSS score of 9.1 and network-accessible attack vector requiring no user interaction or privileges, this represents a critical risk to all unpatched installations.

The WP URL Shortener plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2. This is due to missing or incorrect nonce validation on the 'url_shortener_settings' page. This makes it possible for unauthenticated attackers to update settings and 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 XiSearch bar plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.6. This is due to missing or incorrect nonce validation on the 'xisearch-key-config' page. This makes it possible for unauthenticated attackers to update settings and 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 Yougler Blogger Profile Page plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, v1.01. This is due to missing or incorrect nonce validation on the 'yougler-plugin.php' page. This makes it possible for unauthenticated attackers to update the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The kk Youtube Video plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'kkytv' shortcode in all versions up to, and including, 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 Zen Sticky Social plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.3. This is due to missing or incorrect nonce validation on the 'zen-social-sticky/zen-sticky-social.php' page. This makes it possible for unauthenticated attackers to update settings and 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 Easy Flashcards plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.1. This is due to missing or incorrect nonce validation on the 'ef_settings_submenu' page. This makes it possible for unauthenticated attackers to update settings and 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 StreamWeasels Kick Integration plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘status-classic-offline-text’ parameter in all versions up to, and including, 1.1.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 Click to Chat plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘data-no_number’ parameter in all versions up to, and including, 4.22 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 AI Image Lab - Free AI Image Generator plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.6. This is due to missing or incorrect nonce validation on the 'wpz-ai-images' page. This makes it possible for unauthenticated attackers to update the plugin's API key via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The DIOT SCADA with MQTT plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'diot' shortcode in all versions up to, and including, 1.0.5.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.

A remote code execution vulnerability in all (CVSS 8.1). High severity vulnerability requiring prompt remediation.

The UserPro - Community and User Profile WordPress Plugin plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 5.1.10 via the userpro_fbconnect() function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

AutomatorWP plugin for WordPress versions up to 5.2.3 contains a time-based SQL injection vulnerability in the field_conditions parameter that allows authenticated administrators and higher-privileged users to extract sensitive database information through insufficient input escaping and lack of prepared statements. While the CVSS score of 7.2 is moderately high, exploitation requires administrator-level access, significantly limiting real-world attack surface; no active exploitation in the wild has been confirmed at this time.

A remote code execution vulnerability in File Manager Pro - Filester (CVSS 7.2). High severity vulnerability requiring prompt remediation.

The Seraphinite Accelerator plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.27.21. This is due to missing or incorrect nonce validation on the 'OnAdminApi_CacheOpBegin' function. This makes it possible for unauthenticated attackers to perform several administrative actions, including deleting the cache, via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Stored/Reflected Cross-Site Scripting (XSS) vulnerability in the Drupal etracker module that allows unauthenticated remote attackers to inject malicious scripts into web pages without requiring user interaction. The vulnerability affects etracker versions prior to 3.1.0, enabling attackers to steal session tokens, perform unauthorized actions, or redirect users to malicious sites. The CVSS 7.3 score and network-accessible attack vector indicate this is a significant vulnerability affecting any Drupal installation with the vulnerable etracker module enabled.

Stored/Reflected Cross-Site Scripting (XSS) vulnerability in Drupal Simple Klaro module versions before 1.10.0 that fails to properly neutralize user input during web page generation. An unauthenticated remote attacker can inject malicious scripts that execute in victims' browsers with high impact on confidentiality and integrity, though the attack requires user interaction (clicking a malicious link). The vulnerability has a high CVSS score of 8.8 due to its network-based attack vector and broad scope, but real-world exploitation likelihood depends on KEV/EPSS data not provided in available intelligence.

Cross-Site Scripting (XSS) vulnerability in Drupal's COOKiES Consent Management module that allows unauthenticated remote attackers to inject and execute malicious scripts during web page generation. All versions from 0.0.0 before 1.2.15 are affected. The vulnerability has a high CVSS score of 8.6 with no authentication or user interaction required, enabling attackers to compromise confidentiality, modify page content, and degrade availability. The network-based attack vector and low complexity indicate this is likely actively exploitable in real-world deployments.

Stored/Reflected Cross-Site Scripting (XSS) vulnerability in Drupal's COOKiES Consent Management module (versions before 1.2.15) that allows unauthenticated attackers to inject malicious scripts into web pages due to improper input neutralization. The vulnerability has a CVSS score of 8.6 (High severity) with network-based attack vector requiring no privileges or user interaction, enabling attackers to compromise confidentiality, integrity, and availability of affected sites. No active KEV or widespread public PoC data is available in standard vulnerability databases, suggesting limited real-world exploitation at time of analysis, though the high CVSS and ease of exploitation (AV:N/AC:L/PR:N/UI:N) warrant immediate patching.

A SQL injection vulnerability (CWE-89) exists in the No Boss Calendar Joomla component versions prior to 5.0.7, allowing authenticated users with high privileges to execute arbitrary SQL commands through the id_module parameter. The vulnerability has a CVSS 4.0 score of 8.6 with high impact on confidentiality, integrity, and availability of the database. While the attack requires high-privilege authenticated access, successful exploitation could lead to complete database compromise, data exfiltration, or system takeover.

The Auto Attachments plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.8.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, 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 Game Review Block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and including, 4.8.1 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.

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

The WP Travel Engine plugin for WordPress contains a missing capability check in the delete_package() function, allowing unauthenticated attackers to delete arbitrary posts without authentication. This vulnerability affects all versions up to and including 6.5.1 and results in unauthorized data loss with a CVSS score of 7.5. The vulnerability is network-accessible with no user interaction required, making it a significant integrity risk for WordPress installations running vulnerable plugin versions.

The Telegram for WP plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.6.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, 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 Digital Marketing and Agency Templates Addons for Elementor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.1. This is due to missing or incorrect nonce validation on the import_templates() function. This makes it possible for unauthenticated attackers to trigger an import via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The WP Sliding Login/Dashboard Panel plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1.1. This is due to missing or incorrect nonce validation on the wp_sliding_panel_user_options() function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

The Link Shield plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.5.4. This is due to missing or incorrect nonce validation on the link_shield_menu_options() function. This makes it possible for unauthenticated attackers to update settings and 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 ACF Onyx Poll plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘class’ parameter in all versions up to, and including, 1.1.9 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 REST API | Custom API Generator For Cross Platform And Import Export plugin for WordPress (versions 1.0.0-2.0.3) contains a critical privilege escalation vulnerability where the process_handler() function lacks capability checks, allowing unauthenticated attackers to create administrator accounts via malicious JSON imports. With a CVSS score of 9.8 and network-based attack vector requiring no user interaction, this is a severe, likely actively exploited vulnerability affecting any WordPress installation using vulnerable plugin versions.

The Color Palette plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘hex’ parameter in all versions up to, and including, 4.3.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 Contact Us Page - Contact People plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘style’ parameter in all versions up to, and including, 3.7.4 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.

Multiple SQL injection vulnerabilities in the EuroInformation MoneticoPaiement module before 1.1.1 for PrestaShop allow remote attackers to execute arbitrary SQL commands via the TPE, societe, MAC, reference, or aliascb parameter to transaction.php, validation.php, or callback.php.

Critical unauthenticated SQL injection vulnerability in the JEvents component for Joomla that allows remote attackers to execute arbitrary SQL queries through publicly accessible date range filtering actions. The vulnerability affects JEvents versions before 3.6.88 and 3.6.82.1, enabling attackers to extract sensitive database information, modify data, or potentially achieve remote code execution. With a CVSS score of 9.3 and network-based attack vector requiring no privileges or user interaction, this represents a severe risk to all unpatched Joomla installations using vulnerable JEvents versions.

The WordPress Single Sign-On (SSO) plugin for WordPress is vulnerable to unauthorized access due to a misconfigured capability check on a function in all versions up to, and including, the *.5.3 versions of the plugin. This makes it possible for unauthenticated attackers to extract sensitive data including site content that has been restricted to certain users and/or roles.

A file upload vulnerability in all (CVSS 8.8). High severity vulnerability requiring prompt remediation.

A authentication bypass vulnerability in all (CVSS 9.8). Critical severity with potential for significant impact on affected systems.

Authenticated SQL injection in like-girl 5.2.0 via the /admin/ipAddPost.php endpoint allows remote attackers with administrative privileges to manipulate database queries. Exploit code is publicly available, but no active exploitation has been confirmed by CISA KEV.

SQL injection in kiCode111 like-girl 5.2.0 allows authenticated administrators to execute arbitrary SQL queries via the imgDatd, imgText, or imgUrl parameters in /admin/ImgAddPost.php, leading to potential data theft or modification. Exploit code is publicly available; the vendor did not respond to early disclosure and no patch has been released.

SQL injection in like-girl 5.2.0 allows authenticated admin users to execute arbitrary SQL commands via the /admin/CopyadminPost.php endpoint. A public exploit exists, but no active exploitation has been confirmed. The vendor did not respond to disclosure, leaving the vulnerability unpatched.

SQL injection in like-girl 5.2.0 allows remote authenticated attackers to execute arbitrary SQL commands via the /admin/ImgUpdaPost.php endpoint. Public exploit code is available, but no active exploitation has been confirmed. EPSS score is low (0.08%), indicating limited exploitation likelihood.

SQL injection in kiCode111 like-girl 5.2.0 allows remote authenticated attackers to execute arbitrary SQL commands via multiple parameters in /admin/aboutPost.php. Public exploit code exists, but no active exploitation has been confirmed. EPSS score is low (0.07%), indicating limited exploitation likelihood.

RSTickets! component for Joomla versions 1.9.12 through 3.3.0 contains a stored cross-site scripting (XSS) vulnerability that allows authenticated attackers to inject malicious scripts into the application, which are then executed in the browsers of other users who view the affected content. With a CVSS score of 8.5 and requiring low privilege level plus user interaction, this vulnerability poses a significant risk to Joomla installations using vulnerable RSTickets! versions, particularly in multi-user environments where attackers can escalate privileges or steal administrative credentials.

A remote code execution vulnerability (CVSS 9.2). Critical severity with potential for significant impact on affected systems.

A cross-site scripting vulnerability (CVSS 7.1). High severity vulnerability requiring prompt remediation.

CVE-2025-48446 is an Incorrect Authorization vulnerability (CWE-863) in the Drupal Commerce Alphabank Redirect module that allows unauthenticated attackers to misuse functionality through a network-based attack requiring user interaction. The vulnerability affects Commerce Alphabank Redirect versions prior to 1.0.3, with a CVSS score of 8.8 indicating high severity across confidentiality, integrity, and availability impacts. No public indicators of active exploitation or proof-of-concept code are currently documented, but the high CVSS score and authorization bypass nature warrant immediate patching.

CVE-2025-48445 is an Incorrect Authorization vulnerability (CWE-863) in Drupal Commerce Eurobank (Redirect) payment module versions before 2.1.1 that allows unauthenticated attackers to misuse functionality through a network-based attack requiring user interaction. With a CVSS score of 8.8 and high impact across confidentiality, integrity, and availability, this vulnerability affects payment processing workflows in Drupal e-commerce installations. The vulnerability requires user interaction (UI:R) but no authentication (PR:N), making it exploitable by attackers who can socially engineer victims or intercept redirect flows in payment processing.

The The Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘data-date-*’ parameters in all versions up to, and including, 6.13.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 Xagio SEO plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability in versions up to 7.1.0.16 that allows unauthenticated attackers to inject malicious scripts via the HTTP_REFERER parameter. When users access pages containing injected payloads, the scripts execute in their browsers, potentially enabling session hijacking, credential theft, or malware distribution. The vulnerability was only partially patched in version 7.1.0.0, indicating that complete mitigation requires upgrading to a version beyond 7.1.0.16.

CubeWP - All-in-One Dynamic Content Framework plugin for WordPress versions up to 1.1.23 contains a privilege escalation vulnerability that allows authenticated attackers with Subscriber-level access to elevate their privileges to administrator through arbitrary user meta manipulation. The vulnerability exploits improper access controls on the update_user_meta() function, enabling account takeover and full site compromise. No active exploitation in the wild has been confirmed at this time, but the low attack complexity and high impact make this a critical remediation priority.

The WordPress Automatic Plugin (all versions up to 3.115.0) contains an arbitrary file upload vulnerability in core.php due to insufficient file type validation, allowing authenticated attackers with Author-level or higher privileges to upload malicious files and potentially achieve remote code execution. This is a high-severity vulnerability (CVSS 8.8) affecting a widely-deployed WordPress plugin; real-world exploitation requires valid WordPress credentials at Author level or above, but successful exploitation enables complete server compromise.

WP-DownloadManager plugin for WordPress versions up to 1.68.10 contains an arbitrary file deletion vulnerability (CVE-2025-4799) that allows authenticated administrators to delete any file on the server without directory restrictions. When paired with CVE-2025-4798, attackers can delete critical files like wp-config.php, leading to remote code execution. The vulnerability requires high-privilege administrative access, resulting in a CVSS 7.2 score with high confidentiality, integrity, and availability impact.

The WP-DownloadManager plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 1.68.10. This is due to a lack of restriction on the directory an administrator can select for storing downloads. This makes it possible for authenticated attackers, with Administrator-level access and above, to download and read any file on the server, including system and configuration files.

Cross-site scripting (XSS) in SourceCodester Online Student Clearance System 1.0 allows an authenticated attacker to inject arbitrary web scripts via the 'txtamt' parameter in /Admin/add-fee.php. The exploit has been publicly disclosed, increasing risk of targeted attacks, though EPSS score is low (0.04%).

Critical SQL injection vulnerability in code-projects Restaurant Order System 1.0 affecting the /order.php file, specifically the 'tabidNoti' parameter. Remote unauthenticated attackers 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 code available, making active exploitation likely.

Critical SQL injection vulnerability in code-projects School Fees Payment System version 1.0, specifically in the /branch.php file's ID parameter, allowing remote unauthenticated attackers to execute arbitrary SQL commands. The vulnerability has been publicly disclosed with proof-of-concept exploitation available, and while the CVSS score is 7.3 (High), the unauthenticated network-accessible attack vector combined with confirmed public exploit disclosure indicates active exploitation risk. This affects all deployments of the vulnerable version without patches applied.

Critical SQL injection vulnerability in code-projects School Fees Payment System version 1.0, specifically in the /datatable.php file where the sSortDir_0 parameter is improperly sanitized. An unauthenticated remote attacker can exploit this to execute arbitrary SQL queries, potentially compromising confidentiality, integrity, and availability of the underlying database. The vulnerability has been publicly disclosed with exploit code available, indicating active exploitation risk.

Stored cross-site scripting in PHPGurukul Rail Pass Management System 1.0 allows an authenticated attacker to inject arbitrary JavaScript via the 'fullname' parameter in /admin/add-pass.php. The exploit has been publicly disclosed, increasing the risk of targeted attacks against administrative users.

Cross-site scripting (XSS) in PHPGurukul Rail Pass Management System 1.0 allows remote attackers to inject arbitrary web scripts via the searchdata parameter in /rpms/download-pass.php. The vulnerability is publicly exploited with a disclosed proof-of-concept, though EPSS score is low (0.07%), indicating limited active exploitation.

Cross-site scripting (XSS) in PHPGurukul Restaurant Table Booking System 1.0 allows an authenticated attacker to inject arbitrary JavaScript via the searchdata parameter in /check-status.php. A public exploit exists, but no active exploitation has been reported; EPSS score is low (0.05%).

We are asked to produce a JSON object with specific fields based on the provided CVE data. We must synthesize data from multiple sources: description, CVSS, EPSS, CWE, references, CPE, etc. Output must be plain text strings, no markdown or extra text. Let's analyze the data: - CVE-2025-5973: Vulnerability in PHPGurukul Restaurant Table Booking System 1.0. File /admin/add-table.php, parameter "tableno" leads to cross site scripting (XSS). Attack launched remotely. Exploit disclosed to public. - CVSS: 1.9 (but the vector is CVSS 4.0 with base score? Actually the vector is given: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/... So CVSS 4.0 base score likely 1.9? Wait, the CVSS Score says 1.9, but the vector includes E:P (exploit proof of concept). Base metrics: AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N. The base score from CVSS 4.0 calculator: with VI:L and VC=N, VA=N, PR:H, UI:P, no scope change. That might yield a low score. Actually I need to confirm: CVSS 4.0 base score formula gives 2.0? But provided score is 1.9. We'll use that. - CWE: CWE-79 (Cross-site Scripting). - EPSS: 0.05%, percentile 15% (very low). - POC/Exploit: Publicly available (the description says "The exploit has been disclosed to the public and may be used." So POC=YES. No mention of KEV. So exploitation status: "publicly available exploit code exists" but not actively exploited per CISA KEV. - Reported by: cna@vuldb.com (VulDB is the CNA, not NVD? But NVD enriched). - CPE: cpe:2.3:a:phpgurukul:restaurant_table_booking_system:1.0:*:*:*:*:*:*:* — specific product, version 1.0. - Tags: PHP, XSS - ENISA EUVD ID: EUVD-2025-17812 - Affected versions (EUVD): ["Restaurant Table Booking System 1.0"] - References: from NVD: a GitHub issue (exploit), phpgurukul.com, vuldb.com entries. We need to produce 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. We must follow all precision rules. Step by step: product_name: "PHPGurukul Restaurant Table Booking System" is too long? "1-3 words ONLY." The product is "Restaurant Table Booking System" by PHPGurukul. But we could say "Restaurant Table Booking System" (3 words). That's acceptable. Or "PHPGurukul Table Booking"? But the CPE has "restaurant_table_booking_system". I'll use "Restaurant Table Booking System" as the product name. That's 4 words? "Restaurant" "Table" "Booking" "System" — four words. But the rule says "1-3 words ONLY". So I need to compress. Possibly "Table Booking System"? But maybe they want the primary product name as in the CPE, which is "restaurant_table_booking_system". I'll use "Restaurant Table Booking" (3 words) dropping "System". Actually that might be okay. The instruction: "The specific product or service name affected. Examples: 'Apache Tomcat', 'WordPress', 'Linux Kernel', 'nginx-ui', 'GoAnywhere MFT'. NOT the vulnerability type, NOT the vendor alone, NOT a description." So the product name is "Restaurant Table Booking System" is a bit long. Many CVEs have something like "PHPGurukul Restaurant Table Booking System", but vendor is PHPGurukul, product is Restaurant Table Booking System. I'll go with "Restaurant Table Booking System" (4 words) but the instruction says 1-3 words. I could use "Restaurant Table Booking" as the core product, because "System" is generic. I'll check: In many CVE descriptions, they refer to "PHPGurukul Restaurant Table Booking System". But I can just pick the recognizable product part: "Restaurant Table Booking". That's three words. So product_name: "Restaurant Table Booking". summary: "2-3 sentence plain-language synthesis for security professionals. CRITICAL: Do NOT copy or paraphrase the Description — write an original synthesis using all available data. Do NOT start with 'A vulnerability', 'A problem', 'A flaw', or 'An issue'. Start with the specific impact verb and product, e.g. 'Remote code execution in Apache Tomcat 9.x allows...' or 'Cortex XDR agent on macOS can be disabled by local admins via...'. Explain WHAT the vulnerability is, WHO is affected (specific product/version), and WHAT an attacker can do. Mention if actively exploited (KEV), if POC exists, and EPSS risk if notable." So summary should start with the impact: "Cross-site scripting (XSS) in PHPGurukul Restaurant Table Booking System 1.0 allows..." Then mention that it's in /admin/add-table.php, parameter tableno. Attacker can inject scripts. Mention that exploit is publicly disclosed, but EPSS is very low (0.05%), so low risk of widespread exploitation. No mention of active exploitation. So summary: "Cross-site scripting (XSS) in PHPGurukul Restaurant Table Booking System 1.0 allows remote attackers to inject arbitrary web scripts via the 'tableno' parameter in the /admin/add-table.php endpoint. The attack requires an authenticated administrator to be tricked into clicking a link, and an exploit is publicly available, though EPSS indicates low likelihood of widespread exploitation." But careful: CVSS vector says PR:H (High privileges required), UI:P (User interaction passive). So it's a stored XSS or reflected? The description says "manipulation of the argument tableno leads to cross site scripting", likely reflected or stored in admin panel. The attack requires admin to be logged in and interact. So summary: reflect that. Technical_context: "Explain the underlying technology/library/protocol involved. Use CPE data to identify exact affected products. Reference the CWE to explain the root cause class. Be specific and educational." So mention that it's a PHP-based web application, the admin panel uses PHP, lack of input sanitization leads to CWE-79 XSS. CPE shows version 1.0. Risk_assessment: Compare CVSS vector (AV:N, AC:L, PR:H, UI:P), EPSS 0.05%, no KEV, exploit publicly available. This is a low-severity issue due to high privileges and user interaction required, mitigating widespread risk. "CVSS 4.0 score of 1.9 reflects low impact and high prerequisites; EPSS of 0.05% aligns with low exploitation likelihood. Not known to be actively exploited. Risk is low unless an admin is targeted with phishing." Affected_products: "Write a concise paragraph listing affected products with their versions. Include product name, version range, CPE if available, and link to vendor advisory from references." Only version 1.0. Reference vuldb link: https://vuldb.com/?id.311851 or maybe vendor advisory? The references include phpgurukul.com, but no specific advisory. So I can say: "PHPGurukul Restaurant Table Booking System version 1.0 (CPE: cpe:2.3:a:phpgurukul:restaurant_table_booking_system:1.0) is affected. No vendor advisory with fix version is available; see VulDB entry for details." But careful: the remediation section would mention no patch? We'll see. Patch status from data: no mention of a fix. So patch status: "No vendor-released patch identified at time of analysis." Use that. Remediation: Since no patch, suggest workarounds? "As no vendor patch is available, consider restricting access to the admin panel (/admin/) to trusted users only, and implement input validation or output encoding for the 'tableno' parameter. Alternatively, disable the add-table functionality if not needed." But we need to be specific: "No vendor-released patch identified at time of analysis. Mitigations include restricting HTTP access to /admin/add-table.php to authorized IPs, or applying a web application firewall (WAF) rule to filter malicious scripts in the tableno parameter. Note that these mitigations may not fully prevent exploitation." Also reference VulDB advisory URL. Exploit_scenario: "Brief realistic attack scenario in 2-3 sentences. If POC exists, note that. Factor in attack vector and complexity from CVSS." So: An attacker crafts a malicious URL containing JavaScript in the tableno parameter and sends it to an authenticated administrator. When the admin clicks the link, the script executes in their browser context, potentially stealing session cookies or performing actions on the admin's behalf. A proof-of-concept exploit is publicly available. Exploitation_conditions: "CRITICAL FIELD — security teams make real decisions based on this. Extract SPECIFIC, CONCRETE prerequisites from the CVE description. Name the EXACT product feature, protocol, configuration setting, or deployment mode required. If the description says 'when configured with...' or 'if the X feature is enabled' — that IS the condition. If genuinely no special conditions (AV:N/AC:L/PR:N/UI:N), state: 'No special conditions — remote unauthenticated exploitation against default configurations of [PRODUCT NAME].' Also state what LIMITS exploitation: required user interaction, authentication level, non-default configuration, specific platform/version. These limiting factors help defenders assess realistic risk beyond raw CVSS score. FORBIDDEN generic phrases: 'Network access required.' / 'Specific configuration needed.' / 'Depends on deployment.'" From description and CVSS: PR:H (high privileges) means the attacker needs admin-level authentication. UI:P (user interaction passive) means the victim must interact, likely click a link. So conditions: "The target must be an authenticated administrator user of the Restaurant Table Booking System. The attacker must trick the administrator into interacting with a maliciously crafted link (user interaction). No special deployment configuration is required beyond the default installation of version 1.0." But avoid generic: we have exact product and version. So: "Exploitation requires an authenticated administrator session (PR:H) and user interaction (UI:P) to click a malicious link targeting the /admin/add-table.php endpoint. The vulnerable version 1.0 is susceptible out of the box." Attack_chain: "3-7 short steps separated by ' → ' (arrow), following kill chain phases. Use as many steps as the attack realistically requires. Each step is 3-8 words. Must be grounded in actual CVE data (attack vector, privileges, scope from CVSS)." Phases: based on CVSS, AP:N, PR:H, UI:P. So attacker needs to craft URL, deliver to admin, admin clicks, script executes in admin's browser context. Impact is low (VI:L, no confidentiality or availability impact). So I'll do: "Craft malicious URL with script in tableno param → Deliver link to admin via phishing email → Admin clicks link while authenticated → Browser executes script in admin context → Attacker steals session cookie or performs admin actions". That's 5 steps. Alternatively just 4 steps: "Send malicious link to admin → Admin clicks link → XSS payload executes → Attacker hijacks admin session". That's enough. I'll do 4 steps: "Send crafted link to authenticated admin → Admin clicks the link → Malicious script executes in admin's browser → Attacker leverages admin session to manipulate data". That aligns. Confidence_notes: "1-3 sentences about data completeness and confidence. State what is CONFIRMED (by vendor, NVD, CISA), what is INFERRED (from CVSS vector, description), and what is UNKNOWN or MISSING." NVD entry exists, CVE assigned by VulDB, exploit confirmed via GitHub. Vendor fix unknown. CVSS vector provided by VulDB, likely accurate. So: "Exploit code confirmed publicly on GitHub; CVE details in NVD from VulDB source. No vendor advisory or patch version identified — affected products and fix status are unconfirmed beyond VulDB report. EPSS score is low, consistent with the high privilege requirement." Prevalence: "ONE word ONLY from this exact set: ubiquitous |

Cross-site scripting (XSS) in PHPGurukul Restaurant Table Booking System 1.0 allows authenticated admin users to inject arbitrary web scripts via the fullname parameter in /admin/manage-subadmins.php. Public exploit code exists, but no active exploitation has been reported and EPSS risk is low (0.05%).

SQL injection in code-projects School Fees Payment System 1.0 allows remote authenticated attackers to execute arbitrary SQL commands via the name_startsWith parameter in /ajx.php. A public exploit is available, but no active exploitation has been reported. EPSS score is low (0.09%), indicating limited exploitation likelihood.

Cross-site scripting (XSS) in PHPGurukul Restaurant Table Booking System 1.0 allows authenticated admin users to inject arbitrary web scripts via the 'fullname' parameter in /admin/add-subadmin.php. Public exploit code exists, but no active exploitation has been confirmed. EPSS score is low (0.05%), indicating low exploitation likelihood.

Adobe Commerce versions 2.4.8 and earlier contain an improper authorization vulnerability (CWE-285) that allows unauthenticated attackers to bypass security features and gain unauthorized access to sensitive functionality. This vulnerability has a high integrity impact and can be exploited remotely without user interaction, making it a critical priority for Adobe Commerce administrators. The 8.2 CVSS score combined with the network-accessible attack vector and lack of authentication requirements indicates significant real-world risk.

PHP Local File Inclusion (LFI) vulnerability in LoftOcean TinySalt versions before 3.10.0, caused by improper control of filenames in PHP include/require statements (CWE-98). An unauthenticated remote attacker can exploit this network-accessible vulnerability with moderate complexity to read arbitrary files, execute code, and potentially achieve remote code execution, though exploitation requires specific conditions due to high attack complexity. The vulnerability has not been confirmed as actively exploited in the wild (KEV status unknown), but represents a critical risk for exposed TinySalt installations.

The Premium Addons for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the data-countdown attribute of Countdown widget in all versions up to, and including, 4.11.8 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 Smash Balloon Social Post Feed - Simple Social Feeds for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the data-color attribute in all versions up to, and including, 4.3.1 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 Ultimate Blocks - WordPress Blocks Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via multiple widgets in all versions up to, and including, 3.3.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.

A arbitrary file access vulnerability (CVSS 8.8). Risk factors: public PoC available.

A SQL injection vulnerability in through 1.0.0 does not properly sanitise and escape a parameter (CVSS 7.5). Risk factors: public PoC available.

A critical OS command injection vulnerability exists in Zend.To versions up to 6.10-6 Beta, where unsanitized user input in the 'file_1' parameter of NSSDropoff.php's exec function allows remote, unauthenticated attackers to execute arbitrary system commands with application-level privileges. The vulnerability has been publicly disclosed with working exploits available, making active exploitation probable, though it affects an older software version that has been superseded by newer releases with additional security controls.

The Elementor Website Builder Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘button_text’ parameter in all versions up to, and including, 3.29.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 Bunny’s Print CSS plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.95. This is due to missing or incorrect nonce validation on the pcss_options_subpanel() function. This makes it possible for unauthenticated attackers to update settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

A SQL injection vulnerability in A vulnerability (CVSS 7.3). Risk factors: public PoC available.

The RH - Real Estate WordPress Theme contains an Improper Access Control vulnerability (CWE-269) that allows authenticated subscribers and higher-privileged users to escalate their account privileges to administrator level through the inspiry_update_profile() function. All versions up to and including 4.4.0 are affected; versions 4.4.0 contain a partial patch while 4.4.1 provides complete remediation. With a CVSS score of 8.8 and network-based attack vector requiring only low-privilege authentication, this represents a critical privilege escalation risk for any WordPress installation using this theme.

The Abandoned Cart Pro for WooCommerce plugin (versions ≤9.16.0) contains an authenticated arbitrary file upload vulnerability in the wcap_add_to_cart_popup_upload_files function that lacks file type validation. Authenticated attackers with subscriber-level privileges can upload arbitrary files to the server, potentially enabling remote code execution depending on server configuration. This is a high-severity vulnerability (CVSS 8.8) affecting WooCommerce e-commerce sites; exploitation requires valid user credentials but no user interaction.

HAX CMS PHP versions prior to 11.0.3 contain an OS command injection vulnerability in the `gitImportSite` functionality where insufficient input validation on user-supplied URL parameters allows authenticated attackers to bypass `filter_var` and `strpos` checks and execute arbitrary OS commands via the `set_remote` function's `proc_open` call. An authenticated attacker can leverage this to execute arbitrary commands and exfiltrate output, representing a critical post-authentication code execution risk with high real-world impact due to full OS command execution capability.

HAX CMS PHP allows users to manage their microsite universe with a PHP backend. Prior to version 11.0.0, in the HAX site editor, users can create a website block to load another site in an iframe. The application allows users to supply a target URL in the website block. When the HAX site is visited, the client's browser will query the supplied URL. An authenticated attacker can create a HAX site with a website block pointing at an attacker-controlled server running Responder or a similar tool. The attacker can then conduct a phishing attack by convincing another user to visit their malicious HAX site to harvest credentials. Version 11.0.0 contains a patch for the issue.

HAX CMS PHP allows users to manage their microsite universe with a PHP backend. Prior to version 11.0.0, an authenticated Local File Inclusion (LFI) vulnerability in the HAXCMS saveOutline endpoint allows a low-privileged user to read arbitrary files on the server by manipulating the location field written into site.json. This enables attackers to exfiltrate sensitive system files such as /etc/passwd, application secrets, or configuration files accessible to the web server (www-data). The vulnerability stems from the way the HAXCMS backend handles the location field in the site's outline. When a user sends a POST request to /system/api/saveOutline, the backend stores the provided location value directly into the site.json file associated with the site, without validating or sanitizing the input. Later the location parameter is interpreted by the CMS to resolve and load the content for a given node. If the location field contains a relative path like `../../../etc/passwd`, the application will attempt to read and render that file. Version 11.0.0 fixes the issue.

HAX CMS PHP versions prior to 11.0.0 contain a stored cross-site scripting (XSS) vulnerability in the 'saveNode' and 'saveManifest' endpoints that fails to properly sanitize user input before storing it in the site's JSON schema. An authenticated attacker with low privileges can inject arbitrary JavaScript code through HTML tags (excluding direct <script> tags) that will execute in the context of generated HAX sites, potentially compromising site integrity and user data. The vulnerability has a high CVSS score of 8.5 due to network accessibility, low attack complexity, and cross-site impact, though real-world exploitation requires authenticated access and user interaction with the generated content.

Cross-site scripting in Emlog Pro up to 2.5.7 allows remote authenticated attackers to inject web scripts via the active_post parameter in /admin/article.php. A low-privileged user can craft a malicious URL that, when clicked by an admin, executes arbitrary JavaScript in the admin's browser. Exploit code is publicly available, but EPSS indicates low exploitation probability (0.07%) and the vulnerability is not listed in CISA KEV.