CVE-2009-1038: Multiple SQL injection vulnerabilities in YAP Blog 1.1.1 allow remote attackers to execute arbitrary SQL comma

This month

MEDIUM 6.5DOWNGRADE

CVE-2009-1038 is a medium-severity flaw (CVSS 6.5) affecting yap blog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Multiple SQL injection vulnerabilities in YAP Blog 1.1.1 allow remote attackers to execute arbitrary SQL commands via the (1) image_id parameter to comments.php, and remote authenticated administrators to execute arbitrary SQL commands via the (2) user parameter in a modif action to admin/index.php.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.5 (Medium)
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Weakness	CWE-89
Published	2009-03-20
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: yap

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2009-03-20 18:30 UTCPublished CVE record published
2026-06-16 23:06 UTCUpdated Record last modified

yap yap blog DOWNGRADE

Affected: 1.1.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.1.1

1. Check installed version

apt-cache policy yap-blog || rpm -q yap-blog || yap-blog --version

2. No fixed release: DOWNGRADE to a release before 1.1.1 (Debian / Ubuntu)

apt-cache madison yap-blog sudo apt install yap-blog=<VERSION_BEFORE_1.1.1> sudo apt-mark hold yap-blog

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list yap-blog sudo dnf downgrade yap-blog-<VERSION_BEFORE_1.1.1> sudo dnf versionlock add yap-blog

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: YAP 1.1.1 - 'index.php' Local File Inclusion
Exploit-DB: YAP 1.1.1 - Blind SQL Injection / SQL Injection

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2009-1038?

yap blog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2009-1038 being exploited?

CVE-2009-1038 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2009-1038 affect?

CVE-2009-1038 affects yap blog. Severity is medium (CVSS 6.5). Multiple SQL injection vulnerabilities in YAP Blog 1.1.1 allow remote attackers to execute arbitrary SQL commands via the (1) image_id parameter to comments.php, and remote authenticated administrators to execute arbitrary SQL commands via

How urgent is CVE-2009-1038?

Priority 43/100. Public exploit reference

Software pages

PHP vulnerabilities

References

← Back to latest CVEs