Skip to content
Fencer Intel
medium 6.5

CVE-2019-7738 json

C.P.Sub before 5.3 allows CSRF via a manage.php?p=article_del&id= URI.

published 7y ago modified 4mo ago also EUVD-2019-17267

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

C.P.Sub before 5.3 allows CSRF via a manage.php?p=article_del&id= URI.

Patch / fix

  • c.p.sub_project c.p.sub 5.3

Is CVE-2019-7738 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/cooltey/C.P.Sub/issues/3 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD 2.0 5.8 AV:N/AC:M/Au:N/C:N/I:P/A:P

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.