PHP
Monthly
Local File Inclusion (LFI) vulnerability in the Diza WordPress theme (≤1.3.15) enables low-privileged authenticated attackers to include arbitrary local files, potentially leading to remote code execution, sensitive data exposure, or complete site compromise. The CVSS score of 7.5 reflects high complexity network-based attack requiring authentication. EPSS exploitation probability is low (0.17%, 38th percentile), with no confirmed active exploitation or public proof-of-concept at time of analysis, though the vulnerability has been cataloged by Patchstack's security research team.
SQL injection in itsourcecode Student Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter of /record.php. Exploit code is publicly available, though active exploitation has not been reported and the EPSS exploitation probability is low (0.05%).
SQL injection in Refugee Food Management System 1.0 allows remote attackers to inject arbitrary SQL via the 'a' parameter in /home/home.php. This can lead to unauthorized database access or data manipulation. Exploit code is publicly available, but no active exploitation is confirmed.
SQL injection in Simple Stock System 1.0 allows remote attackers to manipulate the uname parameter in /logout.php, potentially bypassing authentication or altering backend data. Public exploit code is available, though no active exploitation has been reported.
CouchCMS versions up to 2.4 use hard-coded cryptographic keys in the reCAPTCHA handler configuration, allowing remote attackers with high complexity to conduct information disclosure attacks against the reCAPTCHA mechanism. The vulnerability stems from improper handling of K_RECAPTCHA_SITE_KEY and K_RECAPTCHA_SECRET_KEY parameters in couch/config.example.php, and publicly available exploit code exists, though real-world exploitation probability remains low (EPSS 0.06%).
SQL injection in DedeCMS up to version 5.7.118 via the orderby parameter in /freelist_main.php allows authenticated remote attackers to execute arbitrary SQL queries with low impact on confidentiality, integrity, and availability. Publicly available exploit code exists and the vulnerability requires valid user authentication (PR:L) to exploit, significantly limiting real-world risk despite network accessibility.
SQL injection in SeaCMS up to version 13.3 via the e_id parameter in admin_video.php allows authenticated high-privilege attackers to execute arbitrary SQL queries and manipulate database content. The vulnerability requires administrative credentials, limiting real-world impact despite public exploit availability. EPSS score of 0.05% reflects the high privilege requirement needed for exploitation.
SQL injection in SeaCMS up to version 13.3 allows unauthenticated remote attackers to manipulate the `page` and `limit` parameters in the DM player component's database abstraction layer (`js/player/dmplayer/dmku/class/mysqli.class.php`), yielding read and write access to the underlying database. The affected component fails to sanitize pagination inputs before constructing SQL queries, exposing database contents including user credentials and site configuration. A public proof-of-concept exploit has been disclosed, though EPSS remains low at 0.05%, reflecting the product's limited global deployment footprint.
Stored or reflected cross-site scripting (XSS) in Campcodes Complete Online Beauty Parlor Management System 1.0 allows high-privileged authenticated users to inject malicious scripts via the fromdate parameter in /admin/bwdates-reports-details.php, potentially compromising admin sessions or stealing sensitive data. Public exploit code exists, but exploitation requires admin-level privileges and user interaction (likely clicking a malicious link), limiting real-world attack surface despite CVSS 1.9 indicating minimal risk.
We are tasked with producing a JSON object synthesizing data for CVE-2025-14990. CVE ID: CVE-2025-14990 Description: "A security flaw has been discovered in Campcodes Complete Online Beauty Parlor Management System 1.0. Impacted is an unknown function of the file /admin/view-appointment.php. Performing a manipulation of the argument viewid results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks." Given: CVSS Score: 5.5? Actually the CVSS vector provided is a 4.0 vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X The score 5.5 is likely the base score from that vector. Let's assume CVSS 4.0 base score 5.5 (low). The vector indicates: AV:N, AC:L, AT:N, PR:N, UI:N, VC:L/VI:L/VA:L, SC:N/SI:N/SA:N. So it's a network-vector, low attack complexity, no privileges, no user interaction, low impact on vulnerable system (confidentiality, integrity, availability), no impact on subsequent systems. Exploit maturity E:P (proof of concept). Overall, low severity. CWE: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')). SQL injection would normally be CWE-89, but here it's CWE-74, maybe a mistake. We'll note it's SQLi but CWE given is 74. Multi-source intel: EPSS Score: 0.05% (percentile 15%) - very low exploitation probability. POC/Exploit: Publicly available Reported by: cna@vuldb.com CPE: cpe:2.3:a:campcodes:complete_online_beauty_parlor_management_system:1.0:*:*:*:*:*:*:* Tags: PHP, SQLi, Complete Online Beauty Parlor Management System References: github issue, vuldb entries, campcodes homepage. We need to produce fields: product_name: "Complete Online Beauty Parlor Management System" - but that's long, maybe "Beauty Parlor Management System"? The CPE product name is "complete_online_beauty_parlor_management_system". Short: "Complete Online Beauty Parlor Management System" (still long) but they said 1-3 words ONLY. Could be "Beauty Parlor CMS"? But better: "Beauty Parlor Management". However, the exact name is "Complete Online Beauty Parlor Management System". 1-3 words: "Beauty Parlor System"? That might lose clarity. I'll choose "Beauty Parlor Management" (3 words). Or "Complete Online Beauty Parlor" is 3 words? Actually "Complete Online Beauty" is 3 words. But product name: "Campcodes Complete Online Beauty Parlor Management System". I'll pick "Beauty Parlor Management" as shorthand. But the requirement: "1-3 words ONLY. The specific product or service name affected." I'll use "Beauty Parlor MS" (MS for Management System) but that might be too terse. I'll use "Online Beauty Parlor System". That's 4 words? Online (1) Beauty (2) Parlor (3) System (4) -> 4. I could drop "Online": "Beauty Parlor System" is 3. Or "Beauty Parlor CMS"? The software might not be a CMS. I'll go with "Beauty Parlor Management System"? That's 4 words. Maybe "Beauty Parlor Mgmt" but Mgmt is not a word. The rule says "1-3 words ONLY." So I need a very short product name. The vendor is Campcodes, the product is "Complete Online Beauty Parlor Management System". I could say "Beauty Parlor System" (3 words). Yes, that works. I'll use "Beauty Parlor System". The CPE confirms it's version 1.0. summary: Must be original synthesis, not copy of description. Start with specific impact verb and product. E.g., "SQL injection in Beauty Parlor System 1.0 allows remote attackers to manipulate appointment data via viewid parameter." Include EPSS risk: "EPSS predicts very low exploitation probability (0.05%), but a public exploit is available." Mention CWE and KEV? Not in KEV. So "no known active exploitation." Noted: POC is public. technical_context: Mention that it's a PHP web application, the vulnerability is SQL injection in the /admin/view-appointment.php endpoint through the viewid parameter. CWE-74 indicates injection, though SQLi is typically CWE-89. The CPE specifies the exact product and version. The underlying technology: PHP and likely MySQL. risk_assessment: CVSS 4.0 base score 5.5 Medium (Low impact, network, low attack complexity, no privs needed). EPSS 0.05% suggests very unlikely to be exploited in the wild. Not in KEV. POC exists, so possible targeted attacks. The application is a niche beauty parlor management system, likely limited enterprise deployment, so real-world risk is low. SSVC: Exploitation: PoC (public), Automatable: Yes (network, low complexity), Technical Impact: Partial (low impact on confidentiality, integrity, availability). So priority might be moderate only for organizations using this specific software. Compare signals: high ease of exploitation (remote, no auth) but low impact and low prevalence reduces urgency. affected_products: "Campcodes Complete Online Beauty Parlor Management System version 1.0, as per CPE cpe:2.3:a:campcodes:complete_online_beauty_parlor_management_system:1.0. The affected file is /admin/view-appointment.php. No vendor advisory link is provided; references include VulDB entries and a GitHub issue." remediation: No official fix mentioned. Since no vendor advisory is available, suggest: "No vendor patch identified. Mitigation: Disable the affected endpoint /admin/view-appointment.php if not needed, or apply input validation to sanitize the viewid parameter. Restrict network access to the admin panel to trusted IPs. Regularly monitor for SQLi attempts." Since it's a remote unauthenticated injection, the best immediate step is to filter the parameter. Provide specific: "Apply a Web Application Firewall rule to block SQLi patterns on the viewid parameter. Note that the application is from Campcodes, possibly discontinued, so consider replacing the software if it is mission-critical." No patch available. exploit_scenario: "An attacker sends a crafted HTTP GET request to /admin/view-appointment.php?viewid=1' OR '1'='1, exploiting the SQL injection to extract database information, modify appointment records, or potentially gain further access to the underlying server if database privileges allow." exploitation_conditions: From CVSS: AV:N, AC:L, PR:N, UI:N, so no authentication required, remotely exploitable, no user interaction. So conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Beauty Parlor System 1.0. The /admin/view-appointment.php endpoint is publicly accessible and does not require authentication." No limiting factors beyond maybe the admin interface might be somewhat hidden, but default is often accessible. So "unauthenticated". attack_chain: "Reconnaissance of web application → Send malicious SQL payload in viewid parameter → Backend PHP code concatenates input into SQL query → SQL query executed, data exfiltration or modification." More concisely: "Identify /admin/view-appointment.php endpoint → Inject SQL via viewid → Database executes malicious query → Extract/modify appointment data". That's 4 steps. confidence_notes: What is confirmed: Vulnerability in /admin/view-appointment.php of Campcodes Complete Online Beauty Parlor Management System 1.0, disclosed publicly via VulDB and GitHub. Exploit PoC available. Not confirmed: Active exploitation (no KEV). No vendor advisory found; patch status unknown. The CWE is given as CWE-74, but SQL injection is typically CWE-89 — possible misclassification. prevalence: The software is a niche product for beauty parlors, likely low deployment in enterprise environments. So prevalence: "low". Basis: "niche vertical application for small businesses" (max 12 words). I'll use "low" and basis "small business beauty parlor management software". assessed_cvss_vector: Given CVSS 4.0 vector already provided. But the task says: "Your OWN independent CVSS 3.1 base-metric vector ... grounded in the description and exploitation conditions — NOT a copy of any score in the input." So we need to assign a 3.1 vector. According to description: network attack vector, low complexity, no privileges (since it seems unauthenticated — the description doesn't mention auth, but CVSS 4.0 gave PR:N), no user interaction. Impact: SQL injection could lead to data leakage and data manipulation, but CVSS 4.0 gave Low for all. For 3.1, we'd have: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N maybe? Or could be C:L/I:L/A:L? SQLi often leads to database compromise, which can affect availability too. I'll assign C:L/I:L/A:L (all low) as it's a database injection, but scope unchanged. Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. That's a score of 7.3? Actually CVSS 3.1 with C:L/I:L/A:L and everything else low gets 7.3 (High). But original 4.0 score is 5.5. The difference is that 4.0 has separate vulnerable system impact and subsequent impact, and here it's low impact across all three. In 3.1, low impact on all three with AV:N/AC:L/PR:N/UI:N/S:U yields 7.3. That might be too high. The 4.0 vector gave VC:L/VI:L/VA:L (low). Equivalent 3.1 would be the same: C:L/I:L/A:L. So I'll use that. Rationale: "Remote, unauthenticated SQL injection with low impact to confidentiality, integrity, and availability of the database." assessed_cvss40_vector: We can use the same as provided but we'll justify: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. That's fine. Rationale: "Attack requires only network access, no privileges; impact is limited to low on the vulnerable component." Now compile into JSON. Ensure all fields are plain text strings, no arrays. product_name: "Beauty Parlor System" summary: "SQL injection in Campcodes Beauty Parlor System 1.0 allows remote attackers to manipulate or exfiltrate appointment data via the viewid parameter in /admin/view-appointment.php. The vulnerability is remotely exploitable with no authentication, has a publicly available exploit, but EPSS predicts very low (0.05%) exploitation probability. There is no evidence of active exploitation in the wild." technical_context: "The vulnerability exists in the PHP-based Campcodes Complete Online Beauty Parlor Management System 1.0. The offending endpoint /admin/view-appointment.php fails to properly sanitize the 'viewid' input, leading to SQL injection (CWE-74, though typically categorized as CWE-89). The CPE identifies the affected application exactly, and the vulnerability is exploitable against the database back-end, likely MySQL." risk_assessment: "CVSS 4.0 base score 5.5 (Medium) with vector AV:N/AC:L/PR:N/UI:N, indicating easy remote exploitation but only low impact to confidentiality, integrity, and availability. EPSS gives a 0.05% chance of exploitation in the next 30 days, in the 15th percentile, suggesting almost negligible real-world threat. No CISA KEV entry. A public proof-of-concept (PoC) exists, enabling scripted attacks, but the product is a niche beauty parlor management system with likely minimal enterprise footprint. SSVC assessment: Exploitation (PoC), Automatable (Yes), Technical Impact (Partial). Overall, this is a low-priority issue except for organizations actively using this exact software." affected_products: "Campcodes Complete Online Beauty Parlor Management System version 1.0 (cpe:2.3:a:campcodes:
SQL injection in Online Beauty Parlor System 1.0 allows remote attackers to manipulate database queries through the /admin/search-invoices.php endpoint. The vulnerability carries a medium CVSS score, but exploit code is publicly available and no authentication is required, making it easy to attack. No active exploitation in the wild has been confirmed, and the EPSS probability remains low.
Remote SQL injection in Simple Stock System 1.0 allows unauthenticated attackers to manipulate SQL queries via the email parameter in /market/update.php. Public exploit code exists, but no active exploitation has been confirmed. The vulnerability affects the code-projects.org stock management application, potentially exposing database contents.
SQL injection in itsourcecode Student Management System 1.0 allows remote attackers to manipulate database queries via the school_year parameter in /candidates_report.php. Public exploit code is available, enabling unauthorized data access and potential database compromise, though EPSS probability of exploitation is very low (0.05%). No active exploitation has been reported to CISA KEV at this time.
SQL injection in FastAdmin up to version 1.7.0.20250506 allows high-privilege authenticated attackers to execute arbitrary SQL queries via manipulation of the custom/searchField parameter in the selectpage function of the Backend Controller. The vulnerability requires administrator-level privileges and has publicly available exploit code, though the low CVSS score (2.0) and minimal EPSS exploitation probability (0.06%) indicate limited real-world risk despite active disclosure.
Stored cross-site scripting (XSS) in Simple Stock System 1.0 via the /market/chatuser.php endpoint allows remote attackers to inject malicious scripts without authentication. User interaction is required for payload execution. Publicly available exploit code exists; EPSS score of 0.08% indicates low statistical exploitation probability despite XSS classification.
Remote SQL injection in Simple Blood Donor Management System 1.0 allows unauthenticated attackers to execute arbitrary SQL commands via the campaignname parameter in /editedcampaign.php. A public exploit exists, though the vulnerability is not listed in CISA KEV and has a 0.05% EPSS score, suggesting low current exploitation likelihood.
SQL injection in code-projects Simple Blood Donor Management System 1.0 allows remote attackers to manipulate database queries via the Name parameter in /editeddonor.php. Exploit code is publicly available, but no active exploitation known; low real-world impact due to limited product footprint.
SQL injection in Simple Stock System 1.0 allows unauthenticated remote attackers to manipulate database queries via the Username field in /market/signup.php. Public exploit code is available, lowering the barrier to exploitation, though EPSS indicates low probability of widespread attacks.
SQL injection in Campcodes Supplier Management System 1.0 allows remote attackers to manipulate the txtCategoryName parameter in /admin/add_category.php, potentially enabling unauthorized data access or modification. The vulnerability is unauthenticated and exploit code is publicly available, though no active exploitation in the wild has been confirmed. EPSS probability is low (0.05%), indicating limited real-world exploitation likelihood.
SQL injection in Scholars Tracking System 1.0 allows remote attackers to manipulate the post_content parameter in /home.php, potentially extracting or modifying database contents. A public proof-of-concept exploit exists, but no active exploitation is confirmed and EPSS indicates low exploitation probability.
SQL injection in code-projects Scholars Tracking System 1.0 allows remote, unauthenticated attackers to manipulate database queries via the ID parameter of /delete_post.php. A publicly available proof-of-concept exists, but the EPSS score is only 0.05% (15th percentile), indicating a currently low probability of widespread exploitation. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog.
SQL injection in Scholars Tracking System 1.0 allows remote unauthenticated attackers to manipulate the ID parameter in /admin/delete_user.php. The vulnerability enables limited modification or deletion of database records. A public proof-of-concept exploit exists, but no active exploitation in the wild has been confirmed.
SQL injection in code-projects Online Appointment Booking System 1.0 allows high-privilege remote attackers to manipulate the managername parameter in /admin/deletemanager.php, resulting in limited confidentiality and integrity impact. EPSS score of 0.05% and CVSS 2.0 reflect the high privilege requirement (PR:H), which severely constrains real-world exploitability despite public POC availability.
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privileged administrators to execute arbitrary SQL queries via the ID parameter in /admin/userdelete.php. The vulnerability requires administrator access and carries low confidentiality, integrity, and availability impact per CVSS 4.0 scoring. Publicly available exploit code exists, though EPSS scoring (0.01%, percentile 3%) indicates minimal real-world exploitation probability, suggesting the threat is primarily theoretical despite public disclosure.
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privilege administrators to inject malicious SQL via the /admin/stateadd.php endpoint, potentially compromising database integrity and confidentiality. The vulnerability requires administrative privileges to exploit and has a low CVSS score (2.0) due to restricted scope and limited impact, but publicly available exploit code exists. Real-world risk is minimal given the high privilege barrier (PR:H), though organizations running this system should prioritize patching to prevent insider threats.
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privilege administrators to execute arbitrary SQL queries via the /admin/userbuilderdelete.php endpoint. The vulnerability requires authenticated administrator access (CVSS PR:H) and affects only confidentiality and integrity with low impact. Publicly available exploit code exists, though exploitation is limited by the requirement for valid high-privilege credentials and carries low real-world risk due to EPSS score of 0.05% and the attacker profile (malicious insiders with admin accounts).
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privileged administrators to execute arbitrary SQL queries via the /admin/useragentdelete.php endpoint. The vulnerability requires administrator credentials but poses risk to systems where admin accounts may be compromised or where privileged users are untrusted. Publicly available exploit code exists, though EPSS indicates low real-world exploitation probability at 0.05%.
Improper authorization in Campcodes Advanced Voting Management System 1.0 allows authenticated remote attackers to manipulate the ID parameter in /admin/voters_edit.php, resulting in unauthorized modification of voter passwords. The vulnerability affects the Password Handler component and requires valid user credentials to exploit, limiting real-world risk despite public exploit availability. EPSS exploitation probability is low at 0.06 percentile, suggesting this flaw targets specific administrative scenarios rather than representing widespread attack potential.
Unrestricted file upload in SourceCodester Client Database Management System 1.0 via the /user_leads.php endpoint in the Leads Generation Module allows authenticated remote attackers to upload arbitrary files. The vulnerability requires valid user credentials (PR:L in CVSS v4.0) but carries low confidentiality, integrity, and availability impact per the vector. Public exploit code exists, and EPSS score of 0.06% suggests minimal real-world exploitation despite public availability, likely due to the authenticated requirement limiting attack surface.
SQL injection in Campcodes Supplier Management System 1.0 allows remote attackers to query, modify, or delete database records via the cmbAreaCode parameter in /admin/add_retailer.php. Public exploit code is available, but the vulnerability is not known to be actively exploited (CISA KEV). The EPSS exploitation probability is very low (0.05%), indicating limited real-world targeting.
Local file inclusion in the Traveler WordPress theme prior to version 3.2.6 allows unauthenticated remote attackers to include arbitrary local files, potentially leading to information disclosure, remote code execution, or full site compromise. Exploitation requires a high-complexity attack with no user interaction, and the EPSS exploitation probability is low (0.08%), with no known public exploitation or active attacks at the time of analysis.
Local file inclusion in the TieLabs Jannah WordPress theme up to version 7.6.0 allows unauthenticated attackers to include arbitrary local PHP files, potentially leading to sensitive information disclosure (e.g., wp-config.php) or remote code execution via log poisoning. The EPSS score of 0.22% indicates a low probability of imminent exploitation, and no public exploit code or active exploitation has been identified at time of analysis.
Object injection via unsafe deserialization in PDF Invoice Builder for WooCommerce plugin allows authenticated attackers with low privileges to execute arbitrary PHP code, manipulate application objects, or trigger other malicious actions. Affects all versions through 6.5.0. No public exploit identified at time of analysis, with EPSS probability of 0.07% suggesting minimal real-world exploitation activity despite high CVSS score.
Object injection via unsafe deserialization in PDF for WPForms plugin (versions ≤6.5.0) enables authenticated attackers to execute arbitrary PHP code or manipulate application state. The CVSS score of 8.8 reflects network-based exploitation with low complexity requiring only low-privileged authentication. EPSS probability of 0.07% (22nd percentile) suggests limited exploitation likelihood. No public exploit code or CISA KEV listing identified at time of analysis, indicating this remains a theoretical risk requiring proactive patching.
Object injection via unsafe deserialization in PDF for Contact Form 7 WordPress plugin (versions ≤6.5.0) allows authenticated attackers to execute arbitrary PHP code or manipulate application state. Attack requires low-privileged user credentials but no user interaction, with network-accessible attack vector. EPSS probability remains low (0.07%, 22nd percentile) and no active exploitation confirmed at time of analysis. Publicly available exploit code exists per Patchstack disclosure.
PHP object injection in PDF for Gravity Forms + Drag And Drop Template Builder (WordPress plugin) versions up to 6.5.0 allows authenticated attackers with low privileges to execute arbitrary code or manipulate application logic via unsafe deserialization. CVSS 7.5 (High) but EPSS probability of 0.07% (22nd percentile) indicates low observed exploitation likelihood. No public exploit identified at time of analysis, and attack requires high complexity (AC:H) with authenticated access (PR:L).
Local file inclusion in Task Manager WordPress plugin versions ≤3.0.2 enables authenticated attackers with low privileges to read arbitrary files from the web server through improper filename control in PHP include/require statements. Exploitation requires network access with high attack complexity. EPSS score of 0.06% (18th percentile) indicates low probability of mass exploitation. No active exploitation confirmed in CISA KEV at time of analysis, though Patchstack vulnerability database documents this as a disclosed LFI vulnerability.
Local file inclusion in Ray Enterprise Translation WordPress plugin through version 1.7.1 allows remote attackers to read arbitrary files on the server via path traversal in PHP include statements. Despite the moderate CVSS score of 7.5, the EPSS probability of 0.06% (20th percentile) indicates minimal observed exploitation activity in the wild. Patchstack has cataloged this vulnerability with proof-of-concept details, requiring attackers to overcome high complexity conditions and user interaction to achieve impact across confidentiality, integrity, and availability.
Local file inclusion in the Anchor smooth scroll WordPress plugin up to version 1.0.2 allows unauthenticated attackers to read arbitrary files from the server. This can expose sensitive data such as database credentials, and may be escalated to remote code execution under certain server conditions. No active exploitation has been confirmed, and a vendor fix is available.
Local file inclusion in Riode WordPress theme versions ≤1.6.23 allows remote unauthenticated attackers to read arbitrary files from the web server filesystem, potentially exposing configuration files, credentials, and source code. The vulnerability stems from improper filename control in PHP include/require statements. Despite the high CVSS score of 8.1, EPSS indicates only 0.06% exploitation probability (18th percentile), suggesting limited attacker interest. No active exploitation confirmed (not in CISA KEV) and no public POC identified at time of analysis.
Local file inclusion in Thememove MinimogWP WordPress theme versions <=3.9.6 allows unauthenticated attackers over the network to include arbitrary local files, potentially leading to sensitive data disclosure and full server compromise. Exploitation has high attack complexity, and while no active exploitation or public exploit is reported, EPSS shows a low probability of widespread attacks.
Local file inclusion in the Giardino WordPress theme (versions ≤1.1.10) allows unauthenticated attackers to read arbitrary files from the server, such as configuration files and source code. Exploitation requires high attack complexity and can lead to full system compromise if code execution is achieved through chaining. No active exploitation or public exploit has been identified, and the EPSS score is very low (0.08%).
Local file inclusion in axiomthemes Katelyn WordPress theme versions through 1.0.10 allows unauthenticated remote attackers to read arbitrary local files, potentially exposing sensitive data or leading to code execution. Exploitation does not require authentication but has high attack complexity, and no public exploit or active exploitation has been identified.
PHP Local File Inclusion in the Pinevale WordPress theme (<=1.0.14) allows unauthenticated attackers to include arbitrary local files on the server, potentially leading to remote code execution under high-complexity conditions. No active exploitation or public exploit has been identified, but the vulnerability carries a CVSS 8.1 score and affects all prior versions.
Local file inclusion in axiomthemes Renewal WordPress theme versions ≤1.2.2 allows unauthenticated attackers to read arbitrary local files by manipulating input to a PHP include/require statement. Successful exploitation could expose sensitive data such as wp-config.php credentials, with potential limited code execution via log poisoning. EPSS indicates very low exploitation probability (0.08%), and no active exploitation or public proof-of-concept is currently known.
Local file inclusion in the Rosalinda WordPress theme ≤1.2.3 permits unauthenticated attackers to arbitrarily include local files, leading to information disclosure and potential remote code execution. The vulnerability is rated high severity (CVSS 8.1) but has low exploitation likelihood (EPSS 0.08%), and there is no evidence of active exploitation or public exploit code at this time.
Local file inclusion in AncoraThemes Fabrica theme for WordPress <=1.8.1 allows unauthenticated attackers to include and read arbitrary local files on the server, leading to information disclosure and, if chained with techniques like log poisoning or file upload, potential remote code execution. No active exploitation or public exploit has been confirmed; EPSS indicates a low exploitation probability (0.22%).
Unauthenticated remote attackers can exploit a PHP local file inclusion vulnerability in the OnLeash WordPress theme (versions ≤1.5.2) to read sensitive files or achieve remote code execution. No active exploitation or public exploit code has been identified as of this analysis.
Local file inclusion in the MaxCube WordPress theme (versions <= 1.3.1) enables unauthenticated attackers to include arbitrary local files via crafted requests, potentially exposing sensitive data, executing code, and modifying system files. The vulnerability stems from improper validation of filenames in PHP include/require statements. At the time of analysis, no active exploitation or public exploit code is known.
Local file inclusion in AncoraThemes W&D wd theme for WordPress allows unauthenticated attackers to read arbitrary local files and potentially achieve remote code execution. The vulnerability affects versions through 1.0 and has a CVSS 3.1 base score of 8.1, but EPSS predicts a very low exploitation probability (0.08%) with no known public exploits or active exploitation.
Local file inclusion in the Rare Radio WordPress theme (AncoraThemes, versions through 1.0.15.1) exposes WordPress installations to arbitrary PHP file inclusion via unsanitized user input passed to PHP include/require statements. An unauthenticated remote attacker with sufficient complexity can traverse the server filesystem to include PHP files already resident on the server, potentially achieving code execution, credential theft, and full site compromise. No public exploit code or active exploitation has been identified; EPSS is very low at 0.08% (23rd percentile), reflecting limited real-world threat at this time.
Unauthenticated Local File Inclusion in the Panda WordPress theme up to version 1.21 allows remote attackers to read arbitrary server files and potentially escalate to code execution. The vulnerability is not known to be actively exploited and has an EPSS score of 0.08%, indicating low real-world exploitation probability at this time.
Local file inclusion in the Soleil WordPress theme (versions through 1.17) allows unauthenticated attackers to include arbitrary local files via a network request, potentially exposing sensitive data or enabling remote code execution. Exploitation requires high attack complexity, and no active exploitation or public proof-of-concept is currently known.
Local file inclusion in the Tripster WordPress theme (versions <= 1.0.10) allows unauthenticated attackers to read and execute arbitrary files on the server, potentially
Local file inclusion in the Ipharm WordPress theme (versions up to 1.2.3) allows unauthenticated attackers to include arbitrary local files, potentially exposing sensitive data or achieving code execution. No public exploit or active exploitation is known, and EPSS probability is very low (0.08%), though the CVSS score of 8.1 indicates high potential impact.
Local file inclusion in the AxiomThemes HeartStar WordPress theme permits unauthenticated attackers to include arbitrary local files, potentially leading to remote code execution or full site compromise. The vulnerability affects versions up to and including 1.0.14. While there is no confirmed active exploitation or public exploit code, the EPSS score of 0.08% suggests a very low exploitation probability.
We are tasked with synthesizing data about CVE-2025-60044 into a comprehensive analysis. The input includes: CVE ID, description, CVSS 8.1 with vector, CWE-98, EPSS 0.08%, tags, and a reference to Patchstack. No KEV data, no patch details in the input beyond the description saying "through <= 1.1.0". The description says "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability ... allows PHP Local File Inclusion. This issue affects Fribbo: from n/a through <= 1.1.0." Note: The title says Remote File Inclusion but description says Local File Inclusion. Possibly a misclassification? CWE-98 is "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')", which often leads to remote file inclusion if the inclusion is not properly controlled. But the description says PHP Local File Inclusion. We'll handle this. We must output a JSON object with all fields. Let's interpret each: - product_name: "Fribbo" is a WordPress theme. So "Fribbo Theme" or just "Fribbo". Use "Fribbo Theme" maybe. - summary: Original synthesis, not copying description. Start with impact. Impact is local file inclusion (LFI), potentially leading to confidential data exposure, code execution if files are writable, etc. So: "Local file inclusion in the Fribbo WordPress theme (versions <= 1.1.0) allows unauthenticated attackers to include arbitrary local files, potentially exposing sensitive configuration data or enabling remote code execution if coupled with file upload capabilities." Add that EPSS low, no known exploit, not KEV. - technical_context: PHP Include/Require, CWE-98, improper control of filename. WordPress theme, likely uses include() or require() with user-controllable input without proper sanitization. CPE data not provided explicitly, but we can infer from description: "from n/a through <= 1.1.0". So product is "Fribbo" (WordPress theme). Underlying technology: PHP, WordPress themes. CWE-98 refers to PHP Remote File Inclusion but this is LFI; the vulnerability class is file inclusion. Could be RFI if php:// wrappers are disabled or limited. Discuss the root cause. - risk_assessment: CVSS 8.1, AV:N, AC:H, PR:N, UI:N, S:U, C:H/I:H/A:H. AC:H suggests high attack complexity, perhaps due to specific conditions. EPSS 0.08% (low), no KEV, no POC mentioned. SSVC: not given, but we can reason: exploitation status: no known exploit, automatable? AC:H suggests not easily automatable. Technical impact: high (C/I/A all H). So real-world risk may be lower than CVSS suggests because of complexity and low EPSS. Could be a high CVSS but low real risk because product is not widely deployed? Unknown. State that data missing: no patch version specified, no vendor advisory link beyond Patchstack. Patchstack may have provided patch? Not in data. So "patch status unclear; advisory does not mention a fixed version". Also note that CVSS AC:H and no known public exploit. - affected_products: "Fribbo WordPress theme, versions n/a through 1.1.0. Patchstack advisory: [link]." No CPE string given but NVD might have one. - remediation: Not provided. Suggest upgrade to version beyond 1.1.0 if available. As the advisory doesn't specify a fixed version, "contact vendor or monitor Patchstack for update." Workarounds: Disable theme until patch; restrict file access to prevent sensitive file inclusion; disable dangerous PHP functions (allow_url_include) if not needed. But those are generic. Provide actionable. Since no patch, "No official patch available at this time; consider switching to a different theme, or apply web application firewall rules to block file inclusion attempts." - exploit_scenario: An attacker crafts a request to a vulnerable endpoint that includes a local file via directory traversal, e.g., ?file=../../wp-config.php, leading to disclosure of database credentials. - exploitation_conditions: From description, no explicit conditions, but CVSS vector says no user interaction, no privileges, so likely exploitable remotely without authentication. However, AC:H suggests some complexity, maybe the inclusion path is not directly controllable or requires certain PHP configuration. The description: "Improper Control of Filename for Include/Require Statement" means somewhere user input is used to construct a filename for inclusion. So condition: The theme must be active, and the vulnerable parameter must be present, possibly a specific page or AJAX action. So state: "Requires the Fribbo theme (version <= 1.1.0) to be active. Likely exploitable via an HTTP request to a theme component that accepts a filename parameter. No authentication required. High complexity hints at non-trivial exploitation, possibly due to needing to bypass path restrictions or require specific PHP settings (e.g., allow_url_include off)." - attack_chain: Access: Send crafted HTTP request with file path parameter → Exploit: Bypass filename sanitization (if any) → Include local file → Impact: Read sensitive file, achieve code execution via log poisoning or session file inclusion. But we need a chain in kill-chain phases. Let's do: 5-step: Access → Delivery → Exploit → Execution → Impact. Access: Attacker identifies target WordPress site running vulnerable theme. Delivery: Sends HTTP request to vulnerable theme script. Exploit: Parameter containing path traversal triggers file inclusion. Execution: PHP includes arbitrary local file, potentially leading to code execution if php wrappers used. Impact: Disclosure of sensitive data (wp-config.php) or code execution. So chain: "Identify site with Fribbo theme → Send crafted request with malicious file path → Bypass input sanitization to include local file → Execute included code or retrieve file contents → Extract credentials or compromise server." Alternatively, more concise: "Send HTTP request with ‘file’ parameter containing path traversal → Theme includes arbitrary PHP file → Read sensitive file or execute code." - confidence_notes: "Vulnerability reported by Patchstack, but no fixed version listed. Affected version range confirmed by advisory. No CISA KEV or public exploit. CVSS 8.1 indicates high impact but high complexity; EPSS low, suggesting limited real-world threat." I need to be specific: what's confirmed, inferred, unknown. - prevalence: Fribbo is a niche WordPress theme. Likely low prevalence. I'll go with "low". Prevalence_basis: "niche WordPress theme, presumably limited installation base." - assessed_cvss_vector: The existing vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Let's reassess: Attack vector is network (AV:N) as it's a WordPress theme accessible over the internet. Attack complexity high (AC:H) because exploitation might require specific conditions like certain PHP functions not disabled, or the include path must be constructed precisely. Now, what about impact? LFI can lead to reading arbitrary files, so C:H? If you read wp-config.php, yes, confidentiality high. Integrity high? If you can include a log file with PHP code, you could corrupt log files, but that's often not direct integrity impact. However, LFI can lead to RCE, and RCE can mess with system integrity. The CVSS given has C/I/A all High. Could be too aggressive. If only reading files, only C:H. But description says "file inclusion" which might include ability to include any local file, and if combined with file upload, could include a malicious file. But the base vulnerability only allows including local files that already exist, so integrity and availability impacts are less likely unless you can include a file that performs actions. Conservative: C:H, I:L, A:L? But the CVSS from the reporter is 8.1. I might assess slightly lower. Let's set AV:N, AC:H, PR:N, UI:N, S:U. Impact: C:H, I:L, A:L perhaps, but based on typical LFI, it's often confidentiality only unless there is a way to get code execution. If LFI leads to RCE via PHP wrappers (expect://, data://, etc.), that could give full impact. The description says "PHP Local File Inclusion" not Remote, but with wrappers it could be remote code. So the reporter might be assuming worst case. I'll keep assessed vector as close to theirs but justify if any difference. I'll say "AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H" but note that AC:H due to requirement that vulnerable parameter exists and PHP configuration might restrict wrappers. So assessed_cvss_vector: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H". Rationale: "Network-accessible theme with high complexity; full impact if successful, though integrity and availability depend on included file's content." Actually, we can create our own assessment: I'll use AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L, but they gave 8.1 with all High, so I'll stick with the given but acknowledge. I'll set the assessed vector to same as provided, as it's plausible if RCE possible. I'll note in rationale. - assessed_cvss40_vector: Map to 4.0: AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Scope unchanged, so subsequent all N. AT:N. Precision rules: Exploitation status: neither KEV nor POC, so "no public exploit identified at time of analysis". Patch status: from the description, "through <= 1.1.0" means version 1.1.0 and below are affected. No fix version given, so "Patch available per vendor advisory" (Patchstack advisory might mention fix? The reference URL is Patchstack, but we don't have content. It says "Patch available" in the input? The input does not say patch available. It just gives a vulnerability report. So we cannot confirm patch. Use: "No vendor-released patch identified at time of analysis" but we only have the advisory from Patchstack, which might have a fix? We don't know. So I'll state: "No patch version confirmed; Patchstack advisory may have update details but not provided." In field, I'll write "Vendor patch status unclear; advisory from Patchstack does not specify a fixed version." So in remediation, advise checking Patchstack. Prevalence: "low" and basis: "obscure WordPress theme". Let's craft each field. product_name: "Fribbo Theme" (1-3 words: "Fribbo" alone is enough? I'll use "Fribbo" as product name, but add Theme for clarity: "Fribbo") summary: "Local file inclusion in Fribbo WordPress theme (<=1.1.0) enables unauthenticated attackers to read arbitrary files on the server, potentially leading to sensitive data exposure or code execution if combined with file upload or log manipulation. No active exploitation or public exploit is known, and EPSS indicates low exploitation probability." technical_context: "The vulnerability arises from improper validation of user-supplied input used in PHP include/require statements, classified as CWE-98. The Fribbo theme, likely a commercial or niche WordPress product, fails to sanitize filenames passed to inclusion functions, allowing path traversal sequences. CPE data is not available, but the affected version range is from initial release up to 1.1.0. The underlying technology is PHP running on a WordPress site, where includes are server-side and do not require user interaction." risk_assessment: "CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates high impact with complex exploitation. EPSS 0.08% (23rd percentile) suggests very low real-world threat. No CISA KEV or public POC known. The high attack complexity likely stems from the need to bypass any path restrictions or use PHP wrappers that might be disabled. This is a classic high-severity but low-risk scenario for most organizations because of product obscurity and lack of exploits. Missing data: No fix version confirmed; the advisory from Patchstack is the sole source." affected_products: "Fribbo WordPress theme, all versions up to and including 1.1.0. Advisory available at Patchstack (https://patchstack.com/database/Wordpress/Theme/fribbo/vulnerability/wordpress-fribbo-theme-1-1-0-local-file-inclusion-vulnerability?_s_id=cve)." remediation: "No fixed version is listed in the advisory. Users should contact AncoraThemes for a patch or update. As an immediate mitigation, deactivate the Fribbo theme and switch
Local file inclusion in the AncoraThemes Wanderic WordPress theme (versions up to and including 1.0.10) allows unauthenticated attackers to include arbitrary local files on the server, potentially leading to full host compromise through information disclosure or remote code execution. Exploitation requires high attack complexity, and no public exploit or confirmed active exploitation has been identified at this time, with EPSS probability at 0.08%.
Local file inclusion in the Chinchilla WordPress theme (version 1.16 and below) allows unauthenticated remote attackers to read arbitrary files on the server, risking information disclosure or remote code execution via log poisoning. The flaw arises from improper filename handling in PHP include/require statements. No public exploit or active exploitation has been identified, and the EPSS percentage remains very low.
Local File Inclusion (LFI) in axiomthemes Lione WordPress theme versions up to 1.16 allows unauthenticated remote attackers to include arbitrary local files via a crafted request. Successful exploitation can lead to sensitive data exposure and, if combined with other attack vectors such as file uploads, remote code execution. Exploitation requires high attack complexity, and no public exploit or active exploitation is currently known; EPSS indicates a low probability of exploitation (0.08%).
Local file inclusion in axiomthemes Spock WordPress theme through version 1.17 allows unauthenticated remote attackers to read arbitrary files on the server, potentially exposing sensitive information. While high complexity limits exploitability, successful exploitation could lead to full system compromise via techniques like log poisoning. No public exploit code or active exploitation has been reported, and EPSS indicates a very low likelihood of real-world attacks.
Local file inclusion in the Aromatica WordPress theme (versions <= 1.8) allows unauthenticated attackers to read arbitrary files on the server, potentially leading to sensitive information disclosure or remote code execution if combined with other techniques. The vulnerability is not known to be actively exploited, with a low exploitation probability (EPSS 0.08%).
Local file inclusion in axiomthemes Athos WordPress theme up to version 1.9 allows unauthenticated attackers to include arbitrary local files, potentially achieving remote code execution and full site compromise. Exploitation requires high attack complexity, and while no public exploit or active exploitation is currently known, the impact is critical if successfully leveraged.
Local file inclusion in axiomthemes Vocal WordPress theme versions up to 1.12 allows unauthenticated attackers to read arbitrary files on the server by manipulating file path parameters in PHP include/require statements. No active exploitation or public exploit code has been reported; EPSS score is very low (0.08%), indicating minimal immediate risk.
Local file inclusion in the EcoGrow WordPress theme (up to version 1.7) allows unauthenticated attackers to include arbitrary local files, potentially exposing sensitive configuration data like wp-config.php. While no active exploitation or public exploit code is known, the high CVSS score reflects possible escalation to full server compromise if the PHP environment supports wrapper-based code execution. The low EPSS score (0.08%) suggests very limited exploitation likelihood at this time.
Local file inclusion in the Manufactory WordPress theme (<=1.4) allows unauthenticated attackers to read arbitrary files from the server. While the CVSS 8.1 indicates high severity, EPSS exploitation probability is low (0.08%) and no public exploit or active exploitation has been identified.
Local file inclusion in the Agricola WordPress theme (version 1.1.0 and below) allows unauthenticated remote attackers to include arbitrary local files, potentially leading to information disclosure and remote code execution if combined with PHP code injection into a readable file. The vulnerability has a high CVSS score (8.1) but is not known to be actively exploited, and EPSS predicts a very low (0.08%) chance of exploitation.
Local file inclusion in Dwell theme for WordPress versions ≤1.7.0 allows remote unauthenticated attackers to read arbitrary files on the server. The vulnerability, identified by Patchstack, carries a CVSS 8.1 but has very low EPSS exploitation probability and no known public exploit or active targeting. Successful exploitation could lead to full compromise if sensitive files are exfiltrated.
Local file inclusion in the Fabric WordPress theme (≤1.5.0) allows unauthenticated attackers to include arbitrary PHP files, leading to potential remote code execution or sensitive data exposure. Exploitation requires high attack complexity, and no public exploit or active exploitation (KEV) has been reported, with EPSS indicating a 0.08% probability of widespread use.
Local file inclusion in the Basil WordPress theme (up to version 1.3.12) allows unauthenticated remote attackers to read arbitrary files from the server. The vulnerability has a CVSS score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) but a very low EPSS probability (0.08%), and no active exploitation or public exploit code has been detected.
Local file inclusion in the Tacticool WordPress theme through version 1.0.13 allows unauthenticated attackers to include arbitrary local files, potentially disclosing sensitive information or executing code. Exploitation requires high attack complexity, and no public exploit or active exploitation is currently reported.
Local file inclusion in the Catamaran WordPress theme up to version 1.15 lets unauthenticated remote attackers read arbitrary server files and, in certain configurations, escalate to full code execution. The vulnerability stems from improper filename control in a PHP include/require statement, exposing websites using the theme to data theft and server compromise. No active exploitation or public exploit code is known, and EPSS probability is low (0.08%).
Local file inclusion in the Lunna WordPress theme (versions ≤1.15) permits unauthenticated remote attackers to include arbitrary local files, leading to sensitive data exposure and potential remote code execution. The vulnerability carries a CVSS score of 8.1, but exploitation requires high attack complexity and has an EPSS probability of just 0.08%, making widespread automated attack improbable.
Local file inclusion in The Gig WordPress theme <=1.18.0 allows unauthenticated attackers to read arbitrary files from the server and potentially escalate to code execution. The flaw arises from improper sanitization of filenames passed to PHP include/require statements, enabling path traversal. No active exploitation or public exploit code is known, and EPSS indicates low exploitation probability.
Local file inclusion in the Anubis WordPress theme up to version 1.25 allows unauthenticated remote attackers to read arbitrary files on the server, potentially exposing sensitive configuration data. Successful exploitation can lead to full compromise if combined with other vulnerabilities, though attack complexity is high. No active exploitation or public exploit code has been reported, and EPSS indicates low likelihood of widespread exploitation.
PHP Local File Inclusion in the axiomthemes Prisma WordPress theme (all versions through 1.10) lets remote unauthenticated attackers coerce the application into including arbitrary local files, exposing sensitive data and potentially achieving code execution via included PHP payloads. Reported by Patchstack, the flaw carries a CVSS 8.1 (high) rating but a low EPSS of 0.08% (23rd percentile), and there is no public exploit identified at time of analysis. Not listed in CISA KEV.
Local File Inclusion in axiomthemes Palatio WordPress theme through version 1.6 allows unauthenticated remote attackers to include arbitrary local files on the server, potentially leading to information disclosure and code execution. The vulnerability has high attack complexity and no user interaction; it has not been observed in active exploitation, and no public exploit code has been identified at time of analysis.
Remote unauthenticated local file inclusion in the FitFlex WordPress theme (version up to 1.6) allows attackers to read arbitrary server-side files, potentially exposing configuration data, credentials, or enabling further exploitation. The vulnerability carries a high CVSS score (8.1) but EPSS prediction is low (0.08%), and no public exploit or active exploitation is confirmed at the time of analysis.
Local File Inclusion in the Pantry WordPress theme through version 1.4 allows unauthenticated attackers to include arbitrary local files, leading to full site compromise – including information disclosure, arbitrary code execution, and complete integrity and availability loss. The vulnerability carries a CVSS base score of 8.1 but has a very low EPSS exploitation probability (0.08%); no active exploitation or public exploit code has been identified at this time.
Local file inclusion in AncoraThemes HealthHub WordPress theme up to version 1.3.0 permits unauthenticated attackers to read arbitrary local files via improper file path handling, potentially enabling remote code execution if a suitable upload or log chain exists. No public exploit code or active exploitation has been identified at time of analysis, and the EPSS score is low (0.08%). The vulnerability carries a CVSS 8.1 base score due to its unauthenticated network vector and high impact, though high attack complexity significantly limits practical exploitation.
Local file inclusion in the Otaku WordPress theme up to version 1.8.0 allows unauthenticated attackers to include arbitrary local PHP files, resulting in information disclosure, credential theft, or remote code execution. Exploitation requires high complexity and no public exploit or active attacks are currently confirmed. The vulnerability affects the AncoraThemes Otaku theme and is tracked as CVE-2025-58896.
Unauthenticated local file inclusion in AncoraThemes Integro WordPress theme ≤1.8.0 allows remote attackers to read arbitrary files on the server or potentially execute code. The vulnerability carries a CVSS 8.1 score but has low exploitation probability (EPSS 0.08%) and no evidence of active exploitation or public exploit code at the time of analysis.
Local file inclusion in the Good Mood WordPress theme (versions up to 1.16) allows unauthenticated attackers to read arbitrary files from the server, with potential for remote code execution if server configuration permits remote file inclusion. No active exploitation or public exploit code has been identified at this time, but the CVSS 8.1 score reflects high potential impact.
Local file inclusion in the Alright WordPress theme (up to version 1.6.1) allows unauthenticated attackers to read arbitrary local files. Exploitation complexity is high (CVSS 8.1), and no public exploit or active exploitation has been identified at time of analysis, but EPSS is low (0.08%).
Local file inclusion in the Tourimo WordPress theme (<=1.2.3) enables unauthenticated remote attackers to read arbitrary files and potentially execute arbitrary PHP code, leading to full site compromise. This vulnerability, reported by Patchstack, carries a CVSS score of 8.1 but has a low EPSS exploitation probability (0.08%), with no evidence of active exploitation or public exploit code.
Local file inclusion in the AncoraThemes Sanger WordPress theme up to version 1.24.0 allows unauthenticated remote attackers to include arbitrary local files, potentially disclosing sensitive data or executing arbitrary code under specific server conditions. No evidence of active exploitation exists, and the EPSS score of 0.08% indicates low likelihood of widespread attacks.
Local file inclusion vulnerability in the AncoraThemes Playful theme for WordPress up to version 1.19.0 allows unauthenticated attackers
Local file inclusion (LFI) in the Axiomthemes Towny WordPress theme <= 1.16 allows unauthenticated attackers to read arbitrary local files on the server, potentially exposing credentials or other sensitive data. The vulnerability has a CVSS base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicating high impact but elevated attack complexity, and an EPSS score of 0.08% suggesting very low likelihood of widespread exploitation. No active exploitation or public proof-of-concept code has been identified at this time.
Local file inclusion in AncoraThemes The Flash theme through version 1.15 enables unauthenticated attackers to read arbitrary files on the server, potentially exposing configuration files and leading to code execution. No public exploit has been identified, and EPSS probability is low (0.08%). The vulnerability is not listed in CISA KEV.
Local file inclusion in AncoraThemes Pathfinder WordPress theme through version 1.16 allows unauthenticated remote attackers to include arbitrary PHP files on the server, potentially leading to complete system compromise via code execution, though high attack complexity and very low exploitation probability (EPSS 0.08%) suggest limited real-world risk without specific server conditions.
Local File Inclusion (LFI) vulnerability in the Diza WordPress theme (≤1.3.15) enables low-privileged authenticated attackers to include arbitrary local files, potentially leading to remote code execution, sensitive data exposure, or complete site compromise. The CVSS score of 7.5 reflects high complexity network-based attack requiring authentication. EPSS exploitation probability is low (0.17%, 38th percentile), with no confirmed active exploitation or public proof-of-concept at time of analysis, though the vulnerability has been cataloged by Patchstack's security research team.
SQL injection in itsourcecode Student Management System 1.0 allows remote attackers to execute arbitrary SQL commands via the ID parameter of /record.php. Exploit code is publicly available, though active exploitation has not been reported and the EPSS exploitation probability is low (0.05%).
SQL injection in Refugee Food Management System 1.0 allows remote attackers to inject arbitrary SQL via the 'a' parameter in /home/home.php. This can lead to unauthorized database access or data manipulation. Exploit code is publicly available, but no active exploitation is confirmed.
SQL injection in Simple Stock System 1.0 allows remote attackers to manipulate the uname parameter in /logout.php, potentially bypassing authentication or altering backend data. Public exploit code is available, though no active exploitation has been reported.
CouchCMS versions up to 2.4 use hard-coded cryptographic keys in the reCAPTCHA handler configuration, allowing remote attackers with high complexity to conduct information disclosure attacks against the reCAPTCHA mechanism. The vulnerability stems from improper handling of K_RECAPTCHA_SITE_KEY and K_RECAPTCHA_SECRET_KEY parameters in couch/config.example.php, and publicly available exploit code exists, though real-world exploitation probability remains low (EPSS 0.06%).
SQL injection in DedeCMS up to version 5.7.118 via the orderby parameter in /freelist_main.php allows authenticated remote attackers to execute arbitrary SQL queries with low impact on confidentiality, integrity, and availability. Publicly available exploit code exists and the vulnerability requires valid user authentication (PR:L) to exploit, significantly limiting real-world risk despite network accessibility.
SQL injection in SeaCMS up to version 13.3 via the e_id parameter in admin_video.php allows authenticated high-privilege attackers to execute arbitrary SQL queries and manipulate database content. The vulnerability requires administrative credentials, limiting real-world impact despite public exploit availability. EPSS score of 0.05% reflects the high privilege requirement needed for exploitation.
SQL injection in SeaCMS up to version 13.3 allows unauthenticated remote attackers to manipulate the `page` and `limit` parameters in the DM player component's database abstraction layer (`js/player/dmplayer/dmku/class/mysqli.class.php`), yielding read and write access to the underlying database. The affected component fails to sanitize pagination inputs before constructing SQL queries, exposing database contents including user credentials and site configuration. A public proof-of-concept exploit has been disclosed, though EPSS remains low at 0.05%, reflecting the product's limited global deployment footprint.
Stored or reflected cross-site scripting (XSS) in Campcodes Complete Online Beauty Parlor Management System 1.0 allows high-privileged authenticated users to inject malicious scripts via the fromdate parameter in /admin/bwdates-reports-details.php, potentially compromising admin sessions or stealing sensitive data. Public exploit code exists, but exploitation requires admin-level privileges and user interaction (likely clicking a malicious link), limiting real-world attack surface despite CVSS 1.9 indicating minimal risk.
We are tasked with producing a JSON object synthesizing data for CVE-2025-14990. CVE ID: CVE-2025-14990 Description: "A security flaw has been discovered in Campcodes Complete Online Beauty Parlor Management System 1.0. Impacted is an unknown function of the file /admin/view-appointment.php. Performing a manipulation of the argument viewid results in sql injection. The attack may be initiated remotely. The exploit has been released to the public and may be used for attacks." Given: CVSS Score: 5.5? Actually the CVSS vector provided is a 4.0 vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X The score 5.5 is likely the base score from that vector. Let's assume CVSS 4.0 base score 5.5 (low). The vector indicates: AV:N, AC:L, AT:N, PR:N, UI:N, VC:L/VI:L/VA:L, SC:N/SI:N/SA:N. So it's a network-vector, low attack complexity, no privileges, no user interaction, low impact on vulnerable system (confidentiality, integrity, availability), no impact on subsequent systems. Exploit maturity E:P (proof of concept). Overall, low severity. CWE: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')). SQL injection would normally be CWE-89, but here it's CWE-74, maybe a mistake. We'll note it's SQLi but CWE given is 74. Multi-source intel: EPSS Score: 0.05% (percentile 15%) - very low exploitation probability. POC/Exploit: Publicly available Reported by: cna@vuldb.com CPE: cpe:2.3:a:campcodes:complete_online_beauty_parlor_management_system:1.0:*:*:*:*:*:*:* Tags: PHP, SQLi, Complete Online Beauty Parlor Management System References: github issue, vuldb entries, campcodes homepage. We need to produce fields: product_name: "Complete Online Beauty Parlor Management System" - but that's long, maybe "Beauty Parlor Management System"? The CPE product name is "complete_online_beauty_parlor_management_system". Short: "Complete Online Beauty Parlor Management System" (still long) but they said 1-3 words ONLY. Could be "Beauty Parlor CMS"? But better: "Beauty Parlor Management". However, the exact name is "Complete Online Beauty Parlor Management System". 1-3 words: "Beauty Parlor System"? That might lose clarity. I'll choose "Beauty Parlor Management" (3 words). Or "Complete Online Beauty Parlor" is 3 words? Actually "Complete Online Beauty" is 3 words. But product name: "Campcodes Complete Online Beauty Parlor Management System". I'll pick "Beauty Parlor Management" as shorthand. But the requirement: "1-3 words ONLY. The specific product or service name affected." I'll use "Beauty Parlor MS" (MS for Management System) but that might be too terse. I'll use "Online Beauty Parlor System". That's 4 words? Online (1) Beauty (2) Parlor (3) System (4) -> 4. I could drop "Online": "Beauty Parlor System" is 3. Or "Beauty Parlor CMS"? The software might not be a CMS. I'll go with "Beauty Parlor Management System"? That's 4 words. Maybe "Beauty Parlor Mgmt" but Mgmt is not a word. The rule says "1-3 words ONLY." So I need a very short product name. The vendor is Campcodes, the product is "Complete Online Beauty Parlor Management System". I could say "Beauty Parlor System" (3 words). Yes, that works. I'll use "Beauty Parlor System". The CPE confirms it's version 1.0. summary: Must be original synthesis, not copy of description. Start with specific impact verb and product. E.g., "SQL injection in Beauty Parlor System 1.0 allows remote attackers to manipulate appointment data via viewid parameter." Include EPSS risk: "EPSS predicts very low exploitation probability (0.05%), but a public exploit is available." Mention CWE and KEV? Not in KEV. So "no known active exploitation." Noted: POC is public. technical_context: Mention that it's a PHP web application, the vulnerability is SQL injection in the /admin/view-appointment.php endpoint through the viewid parameter. CWE-74 indicates injection, though SQLi is typically CWE-89. The CPE specifies the exact product and version. The underlying technology: PHP and likely MySQL. risk_assessment: CVSS 4.0 base score 5.5 Medium (Low impact, network, low attack complexity, no privs needed). EPSS 0.05% suggests very unlikely to be exploited in the wild. Not in KEV. POC exists, so possible targeted attacks. The application is a niche beauty parlor management system, likely limited enterprise deployment, so real-world risk is low. SSVC: Exploitation: PoC (public), Automatable: Yes (network, low complexity), Technical Impact: Partial (low impact on confidentiality, integrity, availability). So priority might be moderate only for organizations using this specific software. Compare signals: high ease of exploitation (remote, no auth) but low impact and low prevalence reduces urgency. affected_products: "Campcodes Complete Online Beauty Parlor Management System version 1.0, as per CPE cpe:2.3:a:campcodes:complete_online_beauty_parlor_management_system:1.0. The affected file is /admin/view-appointment.php. No vendor advisory link is provided; references include VulDB entries and a GitHub issue." remediation: No official fix mentioned. Since no vendor advisory is available, suggest: "No vendor patch identified. Mitigation: Disable the affected endpoint /admin/view-appointment.php if not needed, or apply input validation to sanitize the viewid parameter. Restrict network access to the admin panel to trusted IPs. Regularly monitor for SQLi attempts." Since it's a remote unauthenticated injection, the best immediate step is to filter the parameter. Provide specific: "Apply a Web Application Firewall rule to block SQLi patterns on the viewid parameter. Note that the application is from Campcodes, possibly discontinued, so consider replacing the software if it is mission-critical." No patch available. exploit_scenario: "An attacker sends a crafted HTTP GET request to /admin/view-appointment.php?viewid=1' OR '1'='1, exploiting the SQL injection to extract database information, modify appointment records, or potentially gain further access to the underlying server if database privileges allow." exploitation_conditions: From CVSS: AV:N, AC:L, PR:N, UI:N, so no authentication required, remotely exploitable, no user interaction. So conditions: "No special conditions — remote unauthenticated exploitation against default configurations of Beauty Parlor System 1.0. The /admin/view-appointment.php endpoint is publicly accessible and does not require authentication." No limiting factors beyond maybe the admin interface might be somewhat hidden, but default is often accessible. So "unauthenticated". attack_chain: "Reconnaissance of web application → Send malicious SQL payload in viewid parameter → Backend PHP code concatenates input into SQL query → SQL query executed, data exfiltration or modification." More concisely: "Identify /admin/view-appointment.php endpoint → Inject SQL via viewid → Database executes malicious query → Extract/modify appointment data". That's 4 steps. confidence_notes: What is confirmed: Vulnerability in /admin/view-appointment.php of Campcodes Complete Online Beauty Parlor Management System 1.0, disclosed publicly via VulDB and GitHub. Exploit PoC available. Not confirmed: Active exploitation (no KEV). No vendor advisory found; patch status unknown. The CWE is given as CWE-74, but SQL injection is typically CWE-89 — possible misclassification. prevalence: The software is a niche product for beauty parlors, likely low deployment in enterprise environments. So prevalence: "low". Basis: "niche vertical application for small businesses" (max 12 words). I'll use "low" and basis "small business beauty parlor management software". assessed_cvss_vector: Given CVSS 4.0 vector already provided. But the task says: "Your OWN independent CVSS 3.1 base-metric vector ... grounded in the description and exploitation conditions — NOT a copy of any score in the input." So we need to assign a 3.1 vector. According to description: network attack vector, low complexity, no privileges (since it seems unauthenticated — the description doesn't mention auth, but CVSS 4.0 gave PR:N), no user interaction. Impact: SQL injection could lead to data leakage and data manipulation, but CVSS 4.0 gave Low for all. For 3.1, we'd have: AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N maybe? Or could be C:L/I:L/A:L? SQLi often leads to database compromise, which can affect availability too. I'll assign C:L/I:L/A:L (all low) as it's a database injection, but scope unchanged. Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. That's a score of 7.3? Actually CVSS 3.1 with C:L/I:L/A:L and everything else low gets 7.3 (High). But original 4.0 score is 5.5. The difference is that 4.0 has separate vulnerable system impact and subsequent impact, and here it's low impact across all three. In 3.1, low impact on all three with AV:N/AC:L/PR:N/UI:N/S:U yields 7.3. That might be too high. The 4.0 vector gave VC:L/VI:L/VA:L (low). Equivalent 3.1 would be the same: C:L/I:L/A:L. So I'll use that. Rationale: "Remote, unauthenticated SQL injection with low impact to confidentiality, integrity, and availability of the database." assessed_cvss40_vector: We can use the same as provided but we'll justify: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N. That's fine. Rationale: "Attack requires only network access, no privileges; impact is limited to low on the vulnerable component." Now compile into JSON. Ensure all fields are plain text strings, no arrays. product_name: "Beauty Parlor System" summary: "SQL injection in Campcodes Beauty Parlor System 1.0 allows remote attackers to manipulate or exfiltrate appointment data via the viewid parameter in /admin/view-appointment.php. The vulnerability is remotely exploitable with no authentication, has a publicly available exploit, but EPSS predicts very low (0.05%) exploitation probability. There is no evidence of active exploitation in the wild." technical_context: "The vulnerability exists in the PHP-based Campcodes Complete Online Beauty Parlor Management System 1.0. The offending endpoint /admin/view-appointment.php fails to properly sanitize the 'viewid' input, leading to SQL injection (CWE-74, though typically categorized as CWE-89). The CPE identifies the affected application exactly, and the vulnerability is exploitable against the database back-end, likely MySQL." risk_assessment: "CVSS 4.0 base score 5.5 (Medium) with vector AV:N/AC:L/PR:N/UI:N, indicating easy remote exploitation but only low impact to confidentiality, integrity, and availability. EPSS gives a 0.05% chance of exploitation in the next 30 days, in the 15th percentile, suggesting almost negligible real-world threat. No CISA KEV entry. A public proof-of-concept (PoC) exists, enabling scripted attacks, but the product is a niche beauty parlor management system with likely minimal enterprise footprint. SSVC assessment: Exploitation (PoC), Automatable (Yes), Technical Impact (Partial). Overall, this is a low-priority issue except for organizations actively using this exact software." affected_products: "Campcodes Complete Online Beauty Parlor Management System version 1.0 (cpe:2.3:a:campcodes:
SQL injection in Online Beauty Parlor System 1.0 allows remote attackers to manipulate database queries through the /admin/search-invoices.php endpoint. The vulnerability carries a medium CVSS score, but exploit code is publicly available and no authentication is required, making it easy to attack. No active exploitation in the wild has been confirmed, and the EPSS probability remains low.
Remote SQL injection in Simple Stock System 1.0 allows unauthenticated attackers to manipulate SQL queries via the email parameter in /market/update.php. Public exploit code exists, but no active exploitation has been confirmed. The vulnerability affects the code-projects.org stock management application, potentially exposing database contents.
SQL injection in itsourcecode Student Management System 1.0 allows remote attackers to manipulate database queries via the school_year parameter in /candidates_report.php. Public exploit code is available, enabling unauthorized data access and potential database compromise, though EPSS probability of exploitation is very low (0.05%). No active exploitation has been reported to CISA KEV at this time.
SQL injection in FastAdmin up to version 1.7.0.20250506 allows high-privilege authenticated attackers to execute arbitrary SQL queries via manipulation of the custom/searchField parameter in the selectpage function of the Backend Controller. The vulnerability requires administrator-level privileges and has publicly available exploit code, though the low CVSS score (2.0) and minimal EPSS exploitation probability (0.06%) indicate limited real-world risk despite active disclosure.
Stored cross-site scripting (XSS) in Simple Stock System 1.0 via the /market/chatuser.php endpoint allows remote attackers to inject malicious scripts without authentication. User interaction is required for payload execution. Publicly available exploit code exists; EPSS score of 0.08% indicates low statistical exploitation probability despite XSS classification.
Remote SQL injection in Simple Blood Donor Management System 1.0 allows unauthenticated attackers to execute arbitrary SQL commands via the campaignname parameter in /editedcampaign.php. A public exploit exists, though the vulnerability is not listed in CISA KEV and has a 0.05% EPSS score, suggesting low current exploitation likelihood.
SQL injection in code-projects Simple Blood Donor Management System 1.0 allows remote attackers to manipulate database queries via the Name parameter in /editeddonor.php. Exploit code is publicly available, but no active exploitation known; low real-world impact due to limited product footprint.
SQL injection in Simple Stock System 1.0 allows unauthenticated remote attackers to manipulate database queries via the Username field in /market/signup.php. Public exploit code is available, lowering the barrier to exploitation, though EPSS indicates low probability of widespread attacks.
SQL injection in Campcodes Supplier Management System 1.0 allows remote attackers to manipulate the txtCategoryName parameter in /admin/add_category.php, potentially enabling unauthorized data access or modification. The vulnerability is unauthenticated and exploit code is publicly available, though no active exploitation in the wild has been confirmed. EPSS probability is low (0.05%), indicating limited real-world exploitation likelihood.
SQL injection in Scholars Tracking System 1.0 allows remote attackers to manipulate the post_content parameter in /home.php, potentially extracting or modifying database contents. A public proof-of-concept exploit exists, but no active exploitation is confirmed and EPSS indicates low exploitation probability.
SQL injection in code-projects Scholars Tracking System 1.0 allows remote, unauthenticated attackers to manipulate database queries via the ID parameter of /delete_post.php. A publicly available proof-of-concept exists, but the EPSS score is only 0.05% (15th percentile), indicating a currently low probability of widespread exploitation. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog.
SQL injection in Scholars Tracking System 1.0 allows remote unauthenticated attackers to manipulate the ID parameter in /admin/delete_user.php. The vulnerability enables limited modification or deletion of database records. A public proof-of-concept exploit exists, but no active exploitation in the wild has been confirmed.
SQL injection in code-projects Online Appointment Booking System 1.0 allows high-privilege remote attackers to manipulate the managername parameter in /admin/deletemanager.php, resulting in limited confidentiality and integrity impact. EPSS score of 0.05% and CVSS 2.0 reflect the high privilege requirement (PR:H), which severely constrains real-world exploitability despite public POC availability.
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privileged administrators to execute arbitrary SQL queries via the ID parameter in /admin/userdelete.php. The vulnerability requires administrator access and carries low confidentiality, integrity, and availability impact per CVSS 4.0 scoring. Publicly available exploit code exists, though EPSS scoring (0.01%, percentile 3%) indicates minimal real-world exploitation probability, suggesting the threat is primarily theoretical despite public disclosure.
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privilege administrators to inject malicious SQL via the /admin/stateadd.php endpoint, potentially compromising database integrity and confidentiality. The vulnerability requires administrative privileges to exploit and has a low CVSS score (2.0) due to restricted scope and limited impact, but publicly available exploit code exists. Real-world risk is minimal given the high privilege barrier (PR:H), though organizations running this system should prioritize patching to prevent insider threats.
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privilege administrators to execute arbitrary SQL queries via the /admin/userbuilderdelete.php endpoint. The vulnerability requires authenticated administrator access (CVSS PR:H) and affects only confidentiality and integrity with low impact. Publicly available exploit code exists, though exploitation is limited by the requirement for valid high-privilege credentials and carries low real-world risk due to EPSS score of 0.05% and the attacker profile (malicious insiders with admin accounts).
SQL injection in CodeAstro Real Estate Management System 1.0 allows high-privileged administrators to execute arbitrary SQL queries via the /admin/useragentdelete.php endpoint. The vulnerability requires administrator credentials but poses risk to systems where admin accounts may be compromised or where privileged users are untrusted. Publicly available exploit code exists, though EPSS indicates low real-world exploitation probability at 0.05%.
Improper authorization in Campcodes Advanced Voting Management System 1.0 allows authenticated remote attackers to manipulate the ID parameter in /admin/voters_edit.php, resulting in unauthorized modification of voter passwords. The vulnerability affects the Password Handler component and requires valid user credentials to exploit, limiting real-world risk despite public exploit availability. EPSS exploitation probability is low at 0.06 percentile, suggesting this flaw targets specific administrative scenarios rather than representing widespread attack potential.
Unrestricted file upload in SourceCodester Client Database Management System 1.0 via the /user_leads.php endpoint in the Leads Generation Module allows authenticated remote attackers to upload arbitrary files. The vulnerability requires valid user credentials (PR:L in CVSS v4.0) but carries low confidentiality, integrity, and availability impact per the vector. Public exploit code exists, and EPSS score of 0.06% suggests minimal real-world exploitation despite public availability, likely due to the authenticated requirement limiting attack surface.
SQL injection in Campcodes Supplier Management System 1.0 allows remote attackers to query, modify, or delete database records via the cmbAreaCode parameter in /admin/add_retailer.php. Public exploit code is available, but the vulnerability is not known to be actively exploited (CISA KEV). The EPSS exploitation probability is very low (0.05%), indicating limited real-world targeting.
Local file inclusion in the Traveler WordPress theme prior to version 3.2.6 allows unauthenticated remote attackers to include arbitrary local files, potentially leading to information disclosure, remote code execution, or full site compromise. Exploitation requires a high-complexity attack with no user interaction, and the EPSS exploitation probability is low (0.08%), with no known public exploitation or active attacks at the time of analysis.
Local file inclusion in the TieLabs Jannah WordPress theme up to version 7.6.0 allows unauthenticated attackers to include arbitrary local PHP files, potentially leading to sensitive information disclosure (e.g., wp-config.php) or remote code execution via log poisoning. The EPSS score of 0.22% indicates a low probability of imminent exploitation, and no public exploit code or active exploitation has been identified at time of analysis.
Object injection via unsafe deserialization in PDF Invoice Builder for WooCommerce plugin allows authenticated attackers with low privileges to execute arbitrary PHP code, manipulate application objects, or trigger other malicious actions. Affects all versions through 6.5.0. No public exploit identified at time of analysis, with EPSS probability of 0.07% suggesting minimal real-world exploitation activity despite high CVSS score.
Object injection via unsafe deserialization in PDF for WPForms plugin (versions ≤6.5.0) enables authenticated attackers to execute arbitrary PHP code or manipulate application state. The CVSS score of 8.8 reflects network-based exploitation with low complexity requiring only low-privileged authentication. EPSS probability of 0.07% (22nd percentile) suggests limited exploitation likelihood. No public exploit code or CISA KEV listing identified at time of analysis, indicating this remains a theoretical risk requiring proactive patching.
Object injection via unsafe deserialization in PDF for Contact Form 7 WordPress plugin (versions ≤6.5.0) allows authenticated attackers to execute arbitrary PHP code or manipulate application state. Attack requires low-privileged user credentials but no user interaction, with network-accessible attack vector. EPSS probability remains low (0.07%, 22nd percentile) and no active exploitation confirmed at time of analysis. Publicly available exploit code exists per Patchstack disclosure.
PHP object injection in PDF for Gravity Forms + Drag And Drop Template Builder (WordPress plugin) versions up to 6.5.0 allows authenticated attackers with low privileges to execute arbitrary code or manipulate application logic via unsafe deserialization. CVSS 7.5 (High) but EPSS probability of 0.07% (22nd percentile) indicates low observed exploitation likelihood. No public exploit identified at time of analysis, and attack requires high complexity (AC:H) with authenticated access (PR:L).
Local file inclusion in Task Manager WordPress plugin versions ≤3.0.2 enables authenticated attackers with low privileges to read arbitrary files from the web server through improper filename control in PHP include/require statements. Exploitation requires network access with high attack complexity. EPSS score of 0.06% (18th percentile) indicates low probability of mass exploitation. No active exploitation confirmed in CISA KEV at time of analysis, though Patchstack vulnerability database documents this as a disclosed LFI vulnerability.
Local file inclusion in Ray Enterprise Translation WordPress plugin through version 1.7.1 allows remote attackers to read arbitrary files on the server via path traversal in PHP include statements. Despite the moderate CVSS score of 7.5, the EPSS probability of 0.06% (20th percentile) indicates minimal observed exploitation activity in the wild. Patchstack has cataloged this vulnerability with proof-of-concept details, requiring attackers to overcome high complexity conditions and user interaction to achieve impact across confidentiality, integrity, and availability.
Local file inclusion in the Anchor smooth scroll WordPress plugin up to version 1.0.2 allows unauthenticated attackers to read arbitrary files from the server. This can expose sensitive data such as database credentials, and may be escalated to remote code execution under certain server conditions. No active exploitation has been confirmed, and a vendor fix is available.
Local file inclusion in Riode WordPress theme versions ≤1.6.23 allows remote unauthenticated attackers to read arbitrary files from the web server filesystem, potentially exposing configuration files, credentials, and source code. The vulnerability stems from improper filename control in PHP include/require statements. Despite the high CVSS score of 8.1, EPSS indicates only 0.06% exploitation probability (18th percentile), suggesting limited attacker interest. No active exploitation confirmed (not in CISA KEV) and no public POC identified at time of analysis.
Local file inclusion in Thememove MinimogWP WordPress theme versions <=3.9.6 allows unauthenticated attackers over the network to include arbitrary local files, potentially leading to sensitive data disclosure and full server compromise. Exploitation has high attack complexity, and while no active exploitation or public exploit is reported, EPSS shows a low probability of widespread attacks.
Local file inclusion in the Giardino WordPress theme (versions ≤1.1.10) allows unauthenticated attackers to read arbitrary files from the server, such as configuration files and source code. Exploitation requires high attack complexity and can lead to full system compromise if code execution is achieved through chaining. No active exploitation or public exploit has been identified, and the EPSS score is very low (0.08%).
Local file inclusion in axiomthemes Katelyn WordPress theme versions through 1.0.10 allows unauthenticated remote attackers to read arbitrary local files, potentially exposing sensitive data or leading to code execution. Exploitation does not require authentication but has high attack complexity, and no public exploit or active exploitation has been identified.
PHP Local File Inclusion in the Pinevale WordPress theme (<=1.0.14) allows unauthenticated attackers to include arbitrary local files on the server, potentially leading to remote code execution under high-complexity conditions. No active exploitation or public exploit has been identified, but the vulnerability carries a CVSS 8.1 score and affects all prior versions.
Local file inclusion in axiomthemes Renewal WordPress theme versions ≤1.2.2 allows unauthenticated attackers to read arbitrary local files by manipulating input to a PHP include/require statement. Successful exploitation could expose sensitive data such as wp-config.php credentials, with potential limited code execution via log poisoning. EPSS indicates very low exploitation probability (0.08%), and no active exploitation or public proof-of-concept is currently known.
Local file inclusion in the Rosalinda WordPress theme ≤1.2.3 permits unauthenticated attackers to arbitrarily include local files, leading to information disclosure and potential remote code execution. The vulnerability is rated high severity (CVSS 8.1) but has low exploitation likelihood (EPSS 0.08%), and there is no evidence of active exploitation or public exploit code at this time.
Local file inclusion in AncoraThemes Fabrica theme for WordPress <=1.8.1 allows unauthenticated attackers to include and read arbitrary local files on the server, leading to information disclosure and, if chained with techniques like log poisoning or file upload, potential remote code execution. No active exploitation or public exploit has been confirmed; EPSS indicates a low exploitation probability (0.22%).
Unauthenticated remote attackers can exploit a PHP local file inclusion vulnerability in the OnLeash WordPress theme (versions ≤1.5.2) to read sensitive files or achieve remote code execution. No active exploitation or public exploit code has been identified as of this analysis.
Local file inclusion in the MaxCube WordPress theme (versions <= 1.3.1) enables unauthenticated attackers to include arbitrary local files via crafted requests, potentially exposing sensitive data, executing code, and modifying system files. The vulnerability stems from improper validation of filenames in PHP include/require statements. At the time of analysis, no active exploitation or public exploit code is known.
Local file inclusion in AncoraThemes W&D wd theme for WordPress allows unauthenticated attackers to read arbitrary local files and potentially achieve remote code execution. The vulnerability affects versions through 1.0 and has a CVSS 3.1 base score of 8.1, but EPSS predicts a very low exploitation probability (0.08%) with no known public exploits or active exploitation.
Local file inclusion in the Rare Radio WordPress theme (AncoraThemes, versions through 1.0.15.1) exposes WordPress installations to arbitrary PHP file inclusion via unsanitized user input passed to PHP include/require statements. An unauthenticated remote attacker with sufficient complexity can traverse the server filesystem to include PHP files already resident on the server, potentially achieving code execution, credential theft, and full site compromise. No public exploit code or active exploitation has been identified; EPSS is very low at 0.08% (23rd percentile), reflecting limited real-world threat at this time.
Unauthenticated Local File Inclusion in the Panda WordPress theme up to version 1.21 allows remote attackers to read arbitrary server files and potentially escalate to code execution. The vulnerability is not known to be actively exploited and has an EPSS score of 0.08%, indicating low real-world exploitation probability at this time.
Local file inclusion in the Soleil WordPress theme (versions through 1.17) allows unauthenticated attackers to include arbitrary local files via a network request, potentially exposing sensitive data or enabling remote code execution. Exploitation requires high attack complexity, and no active exploitation or public proof-of-concept is currently known.
Local file inclusion in the Tripster WordPress theme (versions <= 1.0.10) allows unauthenticated attackers to read and execute arbitrary files on the server, potentially
Local file inclusion in the Ipharm WordPress theme (versions up to 1.2.3) allows unauthenticated attackers to include arbitrary local files, potentially exposing sensitive data or achieving code execution. No public exploit or active exploitation is known, and EPSS probability is very low (0.08%), though the CVSS score of 8.1 indicates high potential impact.
Local file inclusion in the AxiomThemes HeartStar WordPress theme permits unauthenticated attackers to include arbitrary local files, potentially leading to remote code execution or full site compromise. The vulnerability affects versions up to and including 1.0.14. While there is no confirmed active exploitation or public exploit code, the EPSS score of 0.08% suggests a very low exploitation probability.
We are tasked with synthesizing data about CVE-2025-60044 into a comprehensive analysis. The input includes: CVE ID, description, CVSS 8.1 with vector, CWE-98, EPSS 0.08%, tags, and a reference to Patchstack. No KEV data, no patch details in the input beyond the description saying "through <= 1.1.0". The description says "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability ... allows PHP Local File Inclusion. This issue affects Fribbo: from n/a through <= 1.1.0." Note: The title says Remote File Inclusion but description says Local File Inclusion. Possibly a misclassification? CWE-98 is "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')", which often leads to remote file inclusion if the inclusion is not properly controlled. But the description says PHP Local File Inclusion. We'll handle this. We must output a JSON object with all fields. Let's interpret each: - product_name: "Fribbo" is a WordPress theme. So "Fribbo Theme" or just "Fribbo". Use "Fribbo Theme" maybe. - summary: Original synthesis, not copying description. Start with impact. Impact is local file inclusion (LFI), potentially leading to confidential data exposure, code execution if files are writable, etc. So: "Local file inclusion in the Fribbo WordPress theme (versions <= 1.1.0) allows unauthenticated attackers to include arbitrary local files, potentially exposing sensitive configuration data or enabling remote code execution if coupled with file upload capabilities." Add that EPSS low, no known exploit, not KEV. - technical_context: PHP Include/Require, CWE-98, improper control of filename. WordPress theme, likely uses include() or require() with user-controllable input without proper sanitization. CPE data not provided explicitly, but we can infer from description: "from n/a through <= 1.1.0". So product is "Fribbo" (WordPress theme). Underlying technology: PHP, WordPress themes. CWE-98 refers to PHP Remote File Inclusion but this is LFI; the vulnerability class is file inclusion. Could be RFI if php:// wrappers are disabled or limited. Discuss the root cause. - risk_assessment: CVSS 8.1, AV:N, AC:H, PR:N, UI:N, S:U, C:H/I:H/A:H. AC:H suggests high attack complexity, perhaps due to specific conditions. EPSS 0.08% (low), no KEV, no POC mentioned. SSVC: not given, but we can reason: exploitation status: no known exploit, automatable? AC:H suggests not easily automatable. Technical impact: high (C/I/A all H). So real-world risk may be lower than CVSS suggests because of complexity and low EPSS. Could be a high CVSS but low real risk because product is not widely deployed? Unknown. State that data missing: no patch version specified, no vendor advisory link beyond Patchstack. Patchstack may have provided patch? Not in data. So "patch status unclear; advisory does not mention a fixed version". Also note that CVSS AC:H and no known public exploit. - affected_products: "Fribbo WordPress theme, versions n/a through 1.1.0. Patchstack advisory: [link]." No CPE string given but NVD might have one. - remediation: Not provided. Suggest upgrade to version beyond 1.1.0 if available. As the advisory doesn't specify a fixed version, "contact vendor or monitor Patchstack for update." Workarounds: Disable theme until patch; restrict file access to prevent sensitive file inclusion; disable dangerous PHP functions (allow_url_include) if not needed. But those are generic. Provide actionable. Since no patch, "No official patch available at this time; consider switching to a different theme, or apply web application firewall rules to block file inclusion attempts." - exploit_scenario: An attacker crafts a request to a vulnerable endpoint that includes a local file via directory traversal, e.g., ?file=../../wp-config.php, leading to disclosure of database credentials. - exploitation_conditions: From description, no explicit conditions, but CVSS vector says no user interaction, no privileges, so likely exploitable remotely without authentication. However, AC:H suggests some complexity, maybe the inclusion path is not directly controllable or requires certain PHP configuration. The description: "Improper Control of Filename for Include/Require Statement" means somewhere user input is used to construct a filename for inclusion. So condition: The theme must be active, and the vulnerable parameter must be present, possibly a specific page or AJAX action. So state: "Requires the Fribbo theme (version <= 1.1.0) to be active. Likely exploitable via an HTTP request to a theme component that accepts a filename parameter. No authentication required. High complexity hints at non-trivial exploitation, possibly due to needing to bypass path restrictions or require specific PHP settings (e.g., allow_url_include off)." - attack_chain: Access: Send crafted HTTP request with file path parameter → Exploit: Bypass filename sanitization (if any) → Include local file → Impact: Read sensitive file, achieve code execution via log poisoning or session file inclusion. But we need a chain in kill-chain phases. Let's do: 5-step: Access → Delivery → Exploit → Execution → Impact. Access: Attacker identifies target WordPress site running vulnerable theme. Delivery: Sends HTTP request to vulnerable theme script. Exploit: Parameter containing path traversal triggers file inclusion. Execution: PHP includes arbitrary local file, potentially leading to code execution if php wrappers used. Impact: Disclosure of sensitive data (wp-config.php) or code execution. So chain: "Identify site with Fribbo theme → Send crafted request with malicious file path → Bypass input sanitization to include local file → Execute included code or retrieve file contents → Extract credentials or compromise server." Alternatively, more concise: "Send HTTP request with ‘file’ parameter containing path traversal → Theme includes arbitrary PHP file → Read sensitive file or execute code." - confidence_notes: "Vulnerability reported by Patchstack, but no fixed version listed. Affected version range confirmed by advisory. No CISA KEV or public exploit. CVSS 8.1 indicates high impact but high complexity; EPSS low, suggesting limited real-world threat." I need to be specific: what's confirmed, inferred, unknown. - prevalence: Fribbo is a niche WordPress theme. Likely low prevalence. I'll go with "low". Prevalence_basis: "niche WordPress theme, presumably limited installation base." - assessed_cvss_vector: The existing vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Let's reassess: Attack vector is network (AV:N) as it's a WordPress theme accessible over the internet. Attack complexity high (AC:H) because exploitation might require specific conditions like certain PHP functions not disabled, or the include path must be constructed precisely. Now, what about impact? LFI can lead to reading arbitrary files, so C:H? If you read wp-config.php, yes, confidentiality high. Integrity high? If you can include a log file with PHP code, you could corrupt log files, but that's often not direct integrity impact. However, LFI can lead to RCE, and RCE can mess with system integrity. The CVSS given has C/I/A all High. Could be too aggressive. If only reading files, only C:H. But description says "file inclusion" which might include ability to include any local file, and if combined with file upload, could include a malicious file. But the base vulnerability only allows including local files that already exist, so integrity and availability impacts are less likely unless you can include a file that performs actions. Conservative: C:H, I:L, A:L? But the CVSS from the reporter is 8.1. I might assess slightly lower. Let's set AV:N, AC:H, PR:N, UI:N, S:U. Impact: C:H, I:L, A:L perhaps, but based on typical LFI, it's often confidentiality only unless there is a way to get code execution. If LFI leads to RCE via PHP wrappers (expect://, data://, etc.), that could give full impact. The description says "PHP Local File Inclusion" not Remote, but with wrappers it could be remote code. So the reporter might be assuming worst case. I'll keep assessed vector as close to theirs but justify if any difference. I'll say "AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H" but note that AC:H due to requirement that vulnerable parameter exists and PHP configuration might restrict wrappers. So assessed_cvss_vector: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H". Rationale: "Network-accessible theme with high complexity; full impact if successful, though integrity and availability depend on included file's content." Actually, we can create our own assessment: I'll use AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L, but they gave 8.1 with all High, so I'll stick with the given but acknowledge. I'll set the assessed vector to same as provided, as it's plausible if RCE possible. I'll note in rationale. - assessed_cvss40_vector: Map to 4.0: AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Scope unchanged, so subsequent all N. AT:N. Precision rules: Exploitation status: neither KEV nor POC, so "no public exploit identified at time of analysis". Patch status: from the description, "through <= 1.1.0" means version 1.1.0 and below are affected. No fix version given, so "Patch available per vendor advisory" (Patchstack advisory might mention fix? The reference URL is Patchstack, but we don't have content. It says "Patch available" in the input? The input does not say patch available. It just gives a vulnerability report. So we cannot confirm patch. Use: "No vendor-released patch identified at time of analysis" but we only have the advisory from Patchstack, which might have a fix? We don't know. So I'll state: "No patch version confirmed; Patchstack advisory may have update details but not provided." In field, I'll write "Vendor patch status unclear; advisory from Patchstack does not specify a fixed version." So in remediation, advise checking Patchstack. Prevalence: "low" and basis: "obscure WordPress theme". Let's craft each field. product_name: "Fribbo Theme" (1-3 words: "Fribbo" alone is enough? I'll use "Fribbo" as product name, but add Theme for clarity: "Fribbo") summary: "Local file inclusion in Fribbo WordPress theme (<=1.1.0) enables unauthenticated attackers to read arbitrary files on the server, potentially leading to sensitive data exposure or code execution if combined with file upload or log manipulation. No active exploitation or public exploit is known, and EPSS indicates low exploitation probability." technical_context: "The vulnerability arises from improper validation of user-supplied input used in PHP include/require statements, classified as CWE-98. The Fribbo theme, likely a commercial or niche WordPress product, fails to sanitize filenames passed to inclusion functions, allowing path traversal sequences. CPE data is not available, but the affected version range is from initial release up to 1.1.0. The underlying technology is PHP running on a WordPress site, where includes are server-side and do not require user interaction." risk_assessment: "CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates high impact with complex exploitation. EPSS 0.08% (23rd percentile) suggests very low real-world threat. No CISA KEV or public POC known. The high attack complexity likely stems from the need to bypass any path restrictions or use PHP wrappers that might be disabled. This is a classic high-severity but low-risk scenario for most organizations because of product obscurity and lack of exploits. Missing data: No fix version confirmed; the advisory from Patchstack is the sole source." affected_products: "Fribbo WordPress theme, all versions up to and including 1.1.0. Advisory available at Patchstack (https://patchstack.com/database/Wordpress/Theme/fribbo/vulnerability/wordpress-fribbo-theme-1-1-0-local-file-inclusion-vulnerability?_s_id=cve)." remediation: "No fixed version is listed in the advisory. Users should contact AncoraThemes for a patch or update. As an immediate mitigation, deactivate the Fribbo theme and switch
Local file inclusion in the AncoraThemes Wanderic WordPress theme (versions up to and including 1.0.10) allows unauthenticated attackers to include arbitrary local files on the server, potentially leading to full host compromise through information disclosure or remote code execution. Exploitation requires high attack complexity, and no public exploit or confirmed active exploitation has been identified at this time, with EPSS probability at 0.08%.
Local file inclusion in the Chinchilla WordPress theme (version 1.16 and below) allows unauthenticated remote attackers to read arbitrary files on the server, risking information disclosure or remote code execution via log poisoning. The flaw arises from improper filename handling in PHP include/require statements. No public exploit or active exploitation has been identified, and the EPSS percentage remains very low.
Local File Inclusion (LFI) in axiomthemes Lione WordPress theme versions up to 1.16 allows unauthenticated remote attackers to include arbitrary local files via a crafted request. Successful exploitation can lead to sensitive data exposure and, if combined with other attack vectors such as file uploads, remote code execution. Exploitation requires high attack complexity, and no public exploit or active exploitation is currently known; EPSS indicates a low probability of exploitation (0.08%).
Local file inclusion in axiomthemes Spock WordPress theme through version 1.17 allows unauthenticated remote attackers to read arbitrary files on the server, potentially exposing sensitive information. While high complexity limits exploitability, successful exploitation could lead to full system compromise via techniques like log poisoning. No public exploit code or active exploitation has been reported, and EPSS indicates a very low likelihood of real-world attacks.
Local file inclusion in the Aromatica WordPress theme (versions <= 1.8) allows unauthenticated attackers to read arbitrary files on the server, potentially leading to sensitive information disclosure or remote code execution if combined with other techniques. The vulnerability is not known to be actively exploited, with a low exploitation probability (EPSS 0.08%).
Local file inclusion in axiomthemes Athos WordPress theme up to version 1.9 allows unauthenticated attackers to include arbitrary local files, potentially achieving remote code execution and full site compromise. Exploitation requires high attack complexity, and while no public exploit or active exploitation is currently known, the impact is critical if successfully leveraged.
Local file inclusion in axiomthemes Vocal WordPress theme versions up to 1.12 allows unauthenticated attackers to read arbitrary files on the server by manipulating file path parameters in PHP include/require statements. No active exploitation or public exploit code has been reported; EPSS score is very low (0.08%), indicating minimal immediate risk.
Local file inclusion in the EcoGrow WordPress theme (up to version 1.7) allows unauthenticated attackers to include arbitrary local files, potentially exposing sensitive configuration data like wp-config.php. While no active exploitation or public exploit code is known, the high CVSS score reflects possible escalation to full server compromise if the PHP environment supports wrapper-based code execution. The low EPSS score (0.08%) suggests very limited exploitation likelihood at this time.
Local file inclusion in the Manufactory WordPress theme (<=1.4) allows unauthenticated attackers to read arbitrary files from the server. While the CVSS 8.1 indicates high severity, EPSS exploitation probability is low (0.08%) and no public exploit or active exploitation has been identified.
Local file inclusion in the Agricola WordPress theme (version 1.1.0 and below) allows unauthenticated remote attackers to include arbitrary local files, potentially leading to information disclosure and remote code execution if combined with PHP code injection into a readable file. The vulnerability has a high CVSS score (8.1) but is not known to be actively exploited, and EPSS predicts a very low (0.08%) chance of exploitation.
Local file inclusion in Dwell theme for WordPress versions ≤1.7.0 allows remote unauthenticated attackers to read arbitrary files on the server. The vulnerability, identified by Patchstack, carries a CVSS 8.1 but has very low EPSS exploitation probability and no known public exploit or active targeting. Successful exploitation could lead to full compromise if sensitive files are exfiltrated.
Local file inclusion in the Fabric WordPress theme (≤1.5.0) allows unauthenticated attackers to include arbitrary PHP files, leading to potential remote code execution or sensitive data exposure. Exploitation requires high attack complexity, and no public exploit or active exploitation (KEV) has been reported, with EPSS indicating a 0.08% probability of widespread use.
Local file inclusion in the Basil WordPress theme (up to version 1.3.12) allows unauthenticated remote attackers to read arbitrary files from the server. The vulnerability has a CVSS score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) but a very low EPSS probability (0.08%), and no active exploitation or public exploit code has been detected.
Local file inclusion in the Tacticool WordPress theme through version 1.0.13 allows unauthenticated attackers to include arbitrary local files, potentially disclosing sensitive information or executing code. Exploitation requires high attack complexity, and no public exploit or active exploitation is currently reported.
Local file inclusion in the Catamaran WordPress theme up to version 1.15 lets unauthenticated remote attackers read arbitrary server files and, in certain configurations, escalate to full code execution. The vulnerability stems from improper filename control in a PHP include/require statement, exposing websites using the theme to data theft and server compromise. No active exploitation or public exploit code is known, and EPSS probability is low (0.08%).
Local file inclusion in the Lunna WordPress theme (versions ≤1.15) permits unauthenticated remote attackers to include arbitrary local files, leading to sensitive data exposure and potential remote code execution. The vulnerability carries a CVSS score of 8.1, but exploitation requires high attack complexity and has an EPSS probability of just 0.08%, making widespread automated attack improbable.
Local file inclusion in The Gig WordPress theme <=1.18.0 allows unauthenticated attackers to read arbitrary files from the server and potentially escalate to code execution. The flaw arises from improper sanitization of filenames passed to PHP include/require statements, enabling path traversal. No active exploitation or public exploit code is known, and EPSS indicates low exploitation probability.
Local file inclusion in the Anubis WordPress theme up to version 1.25 allows unauthenticated remote attackers to read arbitrary files on the server, potentially exposing sensitive configuration data. Successful exploitation can lead to full compromise if combined with other vulnerabilities, though attack complexity is high. No active exploitation or public exploit code has been reported, and EPSS indicates low likelihood of widespread exploitation.
PHP Local File Inclusion in the axiomthemes Prisma WordPress theme (all versions through 1.10) lets remote unauthenticated attackers coerce the application into including arbitrary local files, exposing sensitive data and potentially achieving code execution via included PHP payloads. Reported by Patchstack, the flaw carries a CVSS 8.1 (high) rating but a low EPSS of 0.08% (23rd percentile), and there is no public exploit identified at time of analysis. Not listed in CISA KEV.
Local File Inclusion in axiomthemes Palatio WordPress theme through version 1.6 allows unauthenticated remote attackers to include arbitrary local files on the server, potentially leading to information disclosure and code execution. The vulnerability has high attack complexity and no user interaction; it has not been observed in active exploitation, and no public exploit code has been identified at time of analysis.
Remote unauthenticated local file inclusion in the FitFlex WordPress theme (version up to 1.6) allows attackers to read arbitrary server-side files, potentially exposing configuration data, credentials, or enabling further exploitation. The vulnerability carries a high CVSS score (8.1) but EPSS prediction is low (0.08%), and no public exploit or active exploitation is confirmed at the time of analysis.
Local File Inclusion in the Pantry WordPress theme through version 1.4 allows unauthenticated attackers to include arbitrary local files, leading to full site compromise – including information disclosure, arbitrary code execution, and complete integrity and availability loss. The vulnerability carries a CVSS base score of 8.1 but has a very low EPSS exploitation probability (0.08%); no active exploitation or public exploit code has been identified at this time.
Local file inclusion in AncoraThemes HealthHub WordPress theme up to version 1.3.0 permits unauthenticated attackers to read arbitrary local files via improper file path handling, potentially enabling remote code execution if a suitable upload or log chain exists. No public exploit code or active exploitation has been identified at time of analysis, and the EPSS score is low (0.08%). The vulnerability carries a CVSS 8.1 base score due to its unauthenticated network vector and high impact, though high attack complexity significantly limits practical exploitation.
Local file inclusion in the Otaku WordPress theme up to version 1.8.0 allows unauthenticated attackers to include arbitrary local PHP files, resulting in information disclosure, credential theft, or remote code execution. Exploitation requires high complexity and no public exploit or active attacks are currently confirmed. The vulnerability affects the AncoraThemes Otaku theme and is tracked as CVE-2025-58896.
Unauthenticated local file inclusion in AncoraThemes Integro WordPress theme ≤1.8.0 allows remote attackers to read arbitrary files on the server or potentially execute code. The vulnerability carries a CVSS 8.1 score but has low exploitation probability (EPSS 0.08%) and no evidence of active exploitation or public exploit code at the time of analysis.
Local file inclusion in the Good Mood WordPress theme (versions up to 1.16) allows unauthenticated attackers to read arbitrary files from the server, with potential for remote code execution if server configuration permits remote file inclusion. No active exploitation or public exploit code has been identified at this time, but the CVSS 8.1 score reflects high potential impact.
Local file inclusion in the Alright WordPress theme (up to version 1.6.1) allows unauthenticated attackers to read arbitrary local files. Exploitation complexity is high (CVSS 8.1), and no public exploit or active exploitation has been identified at time of analysis, but EPSS is low (0.08%).
Local file inclusion in the Tourimo WordPress theme (<=1.2.3) enables unauthenticated remote attackers to read arbitrary files and potentially execute arbitrary PHP code, leading to full site compromise. This vulnerability, reported by Patchstack, carries a CVSS score of 8.1 but has a low EPSS exploitation probability (0.08%), with no evidence of active exploitation or public exploit code.
Local file inclusion in the AncoraThemes Sanger WordPress theme up to version 1.24.0 allows unauthenticated remote attackers to include arbitrary local files, potentially disclosing sensitive data or executing arbitrary code under specific server conditions. No evidence of active exploitation exists, and the EPSS score of 0.08% indicates low likelihood of widespread attacks.
Local file inclusion vulnerability in the AncoraThemes Playful theme for WordPress up to version 1.19.0 allows unauthenticated attackers
Local file inclusion (LFI) in the Axiomthemes Towny WordPress theme <= 1.16 allows unauthenticated attackers to read arbitrary local files on the server, potentially exposing credentials or other sensitive data. The vulnerability has a CVSS base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) indicating high impact but elevated attack complexity, and an EPSS score of 0.08% suggesting very low likelihood of widespread exploitation. No active exploitation or public proof-of-concept code has been identified at this time.
Local file inclusion in AncoraThemes The Flash theme through version 1.15 enables unauthenticated attackers to read arbitrary files on the server, potentially exposing configuration files and leading to code execution. No public exploit has been identified, and EPSS probability is low (0.08%). The vulnerability is not listed in CISA KEV.
Local file inclusion in AncoraThemes Pathfinder WordPress theme through version 1.16 allows unauthenticated remote attackers to include arbitrary PHP files on the server, potentially leading to complete system compromise via code execution, though high attack complexity and very low exploitation probability (EPSS 0.08%) suggest limited real-world risk without specific server conditions.