CVE-2018-25240 · threatengine.sh

Home/CVE/Watchr 1.1.0.0 contains a denial of service vulnerability that allows local attackers to crash the application by submit

CVE

↯ PDF report Light Dark

CVE-2018-252401

Watchr 1.1.0.0 contains a denial of service vulnerability that allows local attackers to crash the application by submit

Watchr 1.1.0.0 contains a denial of service vulnerability that allows local attackers to crash the application by submitting an excessively long string to the search functionality. Attackers can paste a buffer of 8145 characters into the search bar and trigger a search operation to cause the application to crash.

MEDIUM · CVSS 6.2 EPSS 0.00017

EPSS exploitation odds0.02% · top 95%

Schedule remediation

Public exploit or PoC is available

No Sigma yet — build one → YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2018-25240, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

▣

Severity & exploitation scoring

View on NVD →

CVSS base score

6.2

MEDIUMCVSS v3.1 · [email protected]

EPSS exploitation probability

0.02%

Top 95%odds of exploitation in the next 30 days

CVSS metric silhouette

shape grows toward worst-case

SSVC triage · cisa-vulnrichment

Exploitation

poc

Automatable

Tech impact

partial

CVSS vector breakdown

Exploitability - how they get in

Attack Vector

Network Adjacent Local Physical

Attack Complexity

Low High

Privileges Required

None Low High

User Interaction

None Required

Scope

Unchanged Changed

Impact - what breaks

Confidentiality

None Low High

Integrity

None Low High

Availability

None Low High

VECTORCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Lifecycle

04 Apr 2026Published to NVD
16 Apr 2026Last modified

Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.

⚠

Public Exploits & PoCs

These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.

poc www.exploit-db.com · 46194↗ www.exploit-db.com

Works? no reports yet

Rating -

View attack path from CVE-2018-25240

◆

ATT&CK techniques

Techniques this CVE enables - linked via CWE → CAPEC → ATT&CK. Pills with a solid outline are named directly in ATT&CK or Nuclei templates (high confidence); the others are linked through weakness mappings.

T1203 · Exploitation for Client Execution

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-456 · Infected Memory CAPEC-CAPEC-679 · Exploitation of Improperly Configured or Implemented Memory Protections

⬡

Weakness Classification

CWE-1260Improper Handling of Overlap Between Protected Memory Ranges

▤

Related CVEs

CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.

CVE-2018-25238 VSCO 1.1.1.0 contains a denial of service vulnerability that allows local attack... same CWE-1260 MEDIUM CVE-2019-1164 An elevation of privilege vulnerability exists when the Windows kernel fails to ... same CWE-1260 HIGH CVE-2019-25559 SpotPaltalk 1.1.5 contains a denial of service vulnerability in the registration... same CWE-1260 MEDIUM CVE-2019-25570 RealTerm Serial Terminal 2.0.0.70 contains a denial of service vulnerability tha... same CWE-1260 MEDIUM

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://www.microsoft.com/store/productId/9PN12GNX62VZ

https://www.vulncheck.com/advisories/watchr-denial-of-service-via-search