CVE-2018-25210

Web-ofisi E-ticaret cross-site scripting (XSS)

8.2 HIGHPublic exploitEPSS 0.27%

Published26 Mar 2026

Description

WebOfisi E-Ticaret 4.0 contains an SQL injection vulnerability in the 'urun' GET parameter of the endpoint that allows unauthenticated attackers to manipulate database queries. Attackers can inject SQL payloads through the 'urun' parameter to execute boolean-based blind, error-based, time-based blind, and stacked query attacks against the backend database.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityLow

AvailabilityNone

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

Affected products

Web-ofisi E-ticaret≤ 4.0.0

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://drive.google.com/file/d/1ZghFSsYto-Vpv3PXunx8xm2g-Gs3HJwz/view?usp=sharingBroken Link
https://www.exploit-db.com/exploits/45897ExploitThird Party AdvisoryVDB Entry
https://www.vulncheck.com/advisories/webofisi-e-ticaret-sql-injection-via-urun-parameterThird Party Advisory
https://www.web-ofisi.comProduct

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2018-25210 being actively exploited?

CVE-2018-25210 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.27%.

How severe is CVE-2018-25210?

CVE-2018-25210 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.27% probability of exploitation.

Which products are affected by CVE-2018-25210?

Affected products include Web-ofisi E-ticaret.

How do I fix CVE-2018-25210?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2018-25210 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.