dbcve.org
Facebook News Feed LikeApplication · Oretnom23

CVE-2024-1028

MEDIUM · 6.1 CVSS v3.1 Published 2024-01-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in SourceCodester Facebook News Feed Like 1.0 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Post Handler. The manipulation of the argument Description with the input <marquee>HACKED</marquee> leads to cross site scripting. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-252301 was assigned to this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored Cross-Site Scripting (XSS) vulnerability in SourceCodester Facebook News Feed Like 1.0 allows remote attackers to inject malicious HTML/JavaScript via the Description parameter in the Post Handler component. The exploit demonstrates injection of `<marquee>HACKED</marquee>`, which executes when other users view the affected post.

MitigationImplement proper input validation and output encoding on the Description field in the Post Handler component, using context-aware sanitization (e.g., HTML entity encoding or an allowlist approach) before storing and rendering user content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Facebook News Feed LikeApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed application
    Locate the Facebook News Feed Like application in your environment. Check the application's source files or admin interface for version information. Look for files or directories associated with 'facebook-news-feed-like' or 'oretnom23' branding.
    Affected if The application is SourceCodester Facebook News Feed Like or Oretnom23 Facebook News Feed Like version 1.0
  2. Locate the Post Handler component
    Search the application codebase for files related to post handling, such as 'post_handler.php', 'post.php', or similar endpoints that process user-submitted posts. Check for functions that handle the Description parameter.
    Affected if The Post Handler component exists and processes user input for post descriptions
  3. Verify the Description field accepts stored input
    Use the application to create a new post and inject a test payload into the Description field, such as '<marquee>TEST</marquee>' or '<img src=x onerror=alert(1)>'. Submit the post and observe whether the input is stored in the database without immediate sanitization.
    Affected if The Description field accepts and stores HTML or JavaScript content without visible sanitization at submission time
  4. Check if stored content renders without encoding
    View the post created in the previous step as a different user or in a fresh session. Examine the page source and rendered output to determine whether the injected HTML tags execute or display as raw text.
    Affected if The injected '<marquee>TEST</marquee>' or similar HTML renders as an active marquee element or the browser executes the injected script
  5. Inspect application response headers and output
    Review the application's HTTP responses when submitting and viewing posts. Check if Content-Security-Policy headers are present and whether the response includes proper Content-Type headers. Examine the HTML output for absence of HTML entity encoding on user content.
    Affected if No HTML entity encoding (e.g., &lt;marquee&gt;) is applied to the Description field content when rendered

You are affected if you have SourceCodester/Oretnom23 Facebook News Feed Like version 1.0 installed and the Description field in the Post Handler stores and displays your input without sanitizing or encoding HTML characters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding on the Description field in the Post Handler component, using context-aware sanitization (e.g., HTML entity encoding or an allowlist approach) before storing and rendering user content.

Fix this in Facebook News Feed Like Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1028 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data